This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: libtool 2.2.6a: LDFLAGS ignored when building a shared lib?

Corinna Vinschen wrote:
> I have a problem using libtool 2.2.6a.  I've just tried to build the
> latest file(1) for Cygwin 1.7 using gcc-4.  Since gcc-4 is still in flux
> I decided to build with a static libgcc.  First I reconfed the file
> source tree so that the latest libtool is used.  This worked fine,
> configure and make succeeded.  However, here's the one puzzeling problem
> I have.  I'm unable to build using the -static-libgcc flag.  I tried to
> add it to LDFLAGS, then to CFLAGS, then to both.  For some reason this
> flag is filtered out when gcc gets called to link the shared lib.
> So there's the `-static-libgcc' twice in the libtool comamnd line when
> called from make.  But when libtool calls gcc, nothing's left of it.  I
> understand why CFLAGS is missing, but why did it filter out LDFLAGS as
> well?  And, if that's normal, why, and how do I workaround that?

I believe it is a long-standing bug, mentioned here:
but IIRC the promised patch was never produced.

Try Ralf's suggested workaround, configuring your entire package with
CC='gcc -static-libcc' and/or CXX='g++ -static-libgcc'.

If that works, then I'll ping Ralf on fixing this bug.


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]