Hi!
[Replying to various things across the thread]
On 2016-02-10 04:53, Vadim Zeitlin wrote:
> On Tue, 9 Feb 2016 21:29:23 -0600 (CST) Bob Friesenhahn
> wrote:
>
> BF> On Wed, 10 Feb 2016, Vadim Zeitlin wrote:
> BF> >
> BF> > Sorry but this is just not true for the MSW DLLs. If the libtool use
On Wed, 10 Feb 2016 10:02:25 +0100 Peter Rosin wrote:
PR> You appear confused (as almost everybody else) about what -no-undefined
PR> means to libtool. The confusion stems from(?) the similarly named linker
PR> option, --no-undefined, which apparently does what people expect from
PR> the libtool
On Wed, 10 Feb 2016, Peter Rosin wrote:
As for your point about non-trivial programs not working without
special treatment, there are a large body of packages that build just
fine using Cygwin on-top of Windows, without much in the way of special
treatment. Cygwin also suffers the from the curse
On 2/9/16, Vadim Zeitlin wrote:
> On Tue, 9 Feb 2016 18:44:24 -0500 Nick Bowler wrote:
> NB> Here's the thing. Libtool is, by default, designed to transparently
> NB> support the case where building a shared library is not possible.
>
> This is, IMO, an obsolete principle to follow. I admit it m
On 2/10/16, Bob Friesenhahn wrote:
> On Wed, 10 Feb 2016, Peter Rosin wrote:
>> I agree wholeheartedly with the notion that --disable-static should end
>> up in a failure and not somehow degrade to a static build anyway. I
>
> Is this not the case? I have seen builds on Windows fail due to using
On Wed, 10 Feb 2016 10:23:00 -0500 Nick Bowler wrote:
NB> On 2/9/16, Vadim Zeitlin wrote:
NB> > On Tue, 9 Feb 2016 18:44:24 -0500 Nick Bowler wrote:
NB> > NB> Here's the thing. Libtool is, by default, designed to transparently
NB> > NB> support the case where building a shared library is not p
On 2/10/16, Peter Rosin wrote:
> Personally, I don't get why the win32 option exist at all. I see no
> reason to discriminate against Windows like that. Make the no-windows-
> purists opt out with no-win32 (or whatever) instead.
What does the win32-dll option actually do? I just learned about i
On 2/10/16, Vadim Zeitlin wrote:
> On Wed, 10 Feb 2016 10:23:00 -0500 Nick Bowler wrote:
> NB> On 2/9/16, Vadim Zeitlin wrote:
> NB> > On Tue, 9 Feb 2016 18:44:24 -0500 Nick Bowler
> NB> > wrote:
> NB> > NB> Here's the thing. Libtool is, by default, designed to
> NB> > NB> transparently suppor
On Wed, 10 Feb 2016 10:29:40 -0500 Nick Bowler wrote:
NB> On 2/10/16, Bob Friesenhahn wrote:
NB> > On Wed, 10 Feb 2016, Peter Rosin wrote:
NB> >> I agree wholeheartedly with the notion that --disable-static should end
NB> >> up in a failure and not somehow degrade to a static build anyway. I
NB>
On Wed, 10 Feb 2016 10:51:02 -0500 Nick Bowler wrote:
NB> The default (on all platforms) is to create both static libraries and,
NB> when possible, shared libraries.
This is not unreasonable (although not obviously the right thing to do
neither IMO), but I'm only speaking, since the beginning o
On 2/10/16, Vadim Zeitlin wrote:
> On Wed, 10 Feb 2016 10:29:40 -0500 Nick Bowler wrote:
> NB> On 2/10/16, Bob Friesenhahn wrote:
> NB> > On Wed, 10 Feb 2016, Peter Rosin wrote:
> NB> >> I agree wholeheartedly with the notion that --disable-static
> NB> >> should end up in a failure and not some
On Wed, 10 Feb 2016 11:02:29 -0500 Nick Bowler wrote:
NB> On 2/10/16, Vadim Zeitlin wrote:
NB> > On Wed, 10 Feb 2016 10:29:40 -0500 Nick Bowler wrote:
NB> > NB> On 2/10/16, Bob Friesenhahn wrote:
NB> > NB> > On Wed, 10 Feb 2016, Peter Rosin wrote:
NB> > NB> >> I agree wholeheartedly with the n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.02.2016 17:38, Bob Friesenhahn wrote:
> On Wed, 10 Feb 2016, Peter Rosin wrote:
>> I agree wholeheartedly with the notion that --disable-static should e
nd
>> up in a failure and not somehow degrade to a static build anyway. I
> Is this not t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.02.2016 6:29, Bob Friesenhahn wrote:
> On Wed, 10 Feb 2016, Vadim Zeitlin wrote:
>>
>> Sorry but this is just not true for the MSW DLLs. If the libtool user
>> tries to build a DLL, you can safely assume that it will not have
>> undefined
>> sy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.02.2016 6:18, Bob Friesenhahn wrote:
> On Tue, 9 Feb 2016, Vadim Zeitlin wrote:
>>
>> 2. Enabling this option is not enough as you must also painstakingly add
>> -no-undefined to all LDFLAGS. Why does libtool need to force you to do
>> it i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.02.2016 18:23, Nick Bowler wrote:
> Libtool will transparently handles this, by not building shared
> libraries when it cannot do so. The idea is that packages can
> still be useful without shared library support. In my experience,
> this wor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.02.2016 6:18, Bob Friesenhahn wrote:
> On Tue, 9 Feb 2016, Vadim Zeitlin wrote:
>>
>> 2. Enabling this option is not enough as you must also painstakingly add
>> -no-undefined to all LDFLAGS. Why does libtool need to force you to do
>> it i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.02.2016 6:29, Bob Friesenhahn wrote:
> On Wed, 10 Feb 2016, Vadim Zeitlin wrote:
>>
>> Sorry but this is just not true for the MSW DLLs. If the libtool user
>> tries to build a DLL, you can safely assume that it will not have
>> undefined
>> sy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.02.2016 6:29, Bob Friesenhahn wrote:
> On Wed, 10 Feb 2016, Vadim Zeitlin wrote:
>>
>> Sorry but this is just not true for the MSW DLLs. If the libtool user
>> tries to build a DLL, you can safely assume that it will not have
>> undefined
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.02.2016 6:18, Bob Friesenhahn wrote:
> On Tue, 9 Feb 2016, Vadim Zeitlin wrote:
>>
>> 2. Enabling this option is not enough as you must also painstakingly add
>> -no-undefined to all LDFLAGS. Why does libtool need to force you to do
>> it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10.02.2016 19:49, Vadim Zeitlin wrote:
> But the problem with not being able to link in static libraries into a DLL
> under MSW (the point (3) of the post which started this thread and the one
> which I said was the most important for me) remains
Hi,
On 10.02.2016 17:49, Vadim Zeitlin wrote:
> *** Warning: Trying to link with static lib archive
> /opt/msw/i686-w64-mingw32/lib/libboost_filesystem.a.
> *** I have the capability to make that library automatically link in when
> *** you link to this library. But I can only do this if you ha
On Wed, 10 Feb 2016, Evgeny Grin wrote:
As result - "-no-undefined" is used only on W32 without any practical
benefit: if lib have some undefined symbols, it will not be build on W32
as shared lib regardless of "-no-undefined" flag. And conditionally used
The "-no-undefined" option is not actu
23 matches
Mail list logo
