From:	cgf AT cygnus DOT com (Christopher Faylor)
Subject:	Re: Problem building the 9/14/98 snapshot
15 Sep 1998 05:50:05 -0700 :
Message-ID:	<19980915083651.A24789.cygnus.cygwin32.developers@cygnus.com>
References:	<3 DOT 0 DOT 5 DOT 32 DOT 19980915154534 DOT 0081a460 AT mail DOT mel DOT cybec DOT com DOT au>
Mime-Version:	1.0
To:	Trevor Yann <TYann AT vet DOT com DOT au>, cygwin32-developers AT cygnus DOT com

On Tue, Sep 15, 1998 at 03:45:34PM +1000, Trevor Yann wrote:
>I had a little trouble building the latest snapshot.
>
>The makefile in the winsup directory contains:
>
>LIBGCC=${shell $(CC_FOR_TARGET) -print-libgcc-file-name}
>
>Unfortunately the gcc that I am using (Mumit's egcs 1.02) prints the
>following for the libgcc filename:
>
>D:\CYGNUS\B19\H-I386~1\lib\gcc-lib\i386-cygwin32\egcs-2.90.27\libgcc.a
>
>Note the backslashes, which are later interpreted as part of an escape
>sequence.
>
>
>I changed the setting in the makefile to:
>
>LIBGCC=${shell $(CC_FOR_TARGET) -print-libgcc-file-name | sed 's,\\,/,g'}
>
>This fixed the problem, but I am not sure whether this is a correct fix or
>whether it should even be necessary.

It is necessary.  Sorry about that.  That was the standard "last minute
change before the release".  I hadn't tried a native build subsequent to
that change.

Anyway, I was trying to avoid multiple calls of gcc/shell.  Does this
work any better?

LIBGCC:=${subst \\,/,${shell $(CC_FOR_TARGET) -print-libgcc-file-name}}

I can't test it right now, but it should work.

-- 
cgf AT cygnus DOT com
http://www.cygnus.com/

- Raw text -