[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Help-glpk] [Fwd: Build glpk as a shared library on Cygwin, MinGW an

From: Jean-Pierre Flori
Subject: Re: [Help-glpk] [Fwd: Build glpk as a shared library on Cygwin, MinGW and similar systems]
Date: Tue, 4 Nov 2014 17:11:28 +0100


I agree, but they may also end up being passed to the linker.
And some of them choke when given flags they don't recognize.
IIRC I had this kind of issues with packages using gcc to link files.

In fact, I just found the following of yours :)

Anyway, if any of our solutions gets merged I'll be very happy.


2014-11-04 17:06 GMT+01:00 Marco Atzeri <address@hidden>:
> On 11/4/2014 3:55 PM, Jean-Pierre Flori wrote:
>> Hi again all,
>> Hopefully, this time my reply will also appear on the help-glpk
>> archive as I subscribed there.
>> As far as Marco's patch is concerned, it is fine and work, but passing
>> -no-undefined directly through LDFLAGS is not the right way to go.
>> The -no-undefined flag is really meant for libtool, not for the linker.
>> In fact the proper way to go would be to put it into
>> something_la_LTFLAGS but this does not work...
>> So the most usual solution is to put it into library_la_LDFLAGS (which
>> is a variation of LDFLAGS but meant for libtool).
> Sorry Jean-Pierre,
> but you are mistaken:
> global LDFLAGS are passed to libtool, as seen in this extract
> of the "src/Makefile" in the build tree.
> libglpk_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) \
>         $(LIBTOOLFLAGS) --mode=link $(CCLD) $(AM_CFLAGS) $(CFLAGS) \
>         $(libglpk_la_LDFLAGS) $(LDFLAGS) -o $@
> Regards
> Marco
> _______________________________________________
> Help-glpk mailing list
> address@hidden

Jean-Pierre Flori

reply via email to

[Prev in Thread] Current Thread [Next in Thread]