Re: MSW DLLs support in libtool

2016-02-12 Thread Evgeny Grin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12.02.2016 0:14, Nick Bowler wrote: > On 2/11/16, Evgeny Grin wrote: >> * change default shared lib mode from "on" to "auto" or "try" and fail >> if shared lib cannot be created when mode is "on". With that logic >> "make" will do what requested

Re: MSW DLLs support in libtool

2016-02-12 Thread Nick Bowler
On 2/12/16, Evgeny Grin wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On 12.02.2016 0:14, Nick Bowler wrote: >> On 2/11/16, Evgeny Grin wrote: >>> * change default shared lib mode from "on" to "auto" or "try" and fail >>> if shared lib cannot be created when mode is "on". With th

Mailing Lists

2016-02-12 Thread martin
Please unsubscribe. ___ https://lists.gnu.org/mailman/listinfo/libtool

Re: MSW DLLs support in libtool

2016-02-12 Thread Evgeny Grin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12.02.2016 0:53, Bob Friesenhahn wrote: > On Thu, 11 Feb 2016, Evgeny Grin wrote: >> On 10.02.2016 18:51, Nick Bowler wrote: >>> The default (on all platforms) is to create both static libraries and, >>> when possible, shared libraries. >> This

Re: MSW DLLs support in libtool

2016-02-12 Thread Evgeny Grin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12.02.2016 10:21, Peter Rosin wrote: > On 2016-02-11 12:23, Evgeny Grin wrote: >> On 11.02.2016 11:03, Peter Rosin wrote: >>> Well said, I would also like to add that libtool -no-undefined *does* *not* >>> imply ld --no-undefined. I.e. If you ad

Re: MSW DLLs support in libtool

2016-02-12 Thread Evgeny Grin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12.02.2016 17:28, Nick Bowler wrote: > On 2/12/16, Evgeny Grin wrote: >> Actually, no. See: > > Just to be sure: > Here you are running libtool installed on the system (by path lookup)... > > [...] >> /bin/sh ../../libtool --tag=CC --mode=

Re: Mailing Lists

2016-02-12 Thread Mike Frysinger
On 12 Feb 2016 15:17, martin wrote: > Please unsubscribe. > > ___ > https://lists.gnu.org/mailman/listinfo/libtool use the link at the bottom of every e-mail to manage your subscription -mike signature.asc Description: Digital signature __

Re: MSW DLLs support in libtool

2016-02-12 Thread Evgeny Grin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 12.02.2016 20:29, Evgeny Grin wrote: > > > On 12.02.2016 17:28, Nick Bowler wrote: >> On 2/12/16, Evgeny Grin wrote: >>> Actually, no. See: > >> Just to be sure: >> Here you are running libtool installed on the system (by path lookup)... >

Re: MSW DLLs support in libtool

2016-02-12 Thread Bob Friesenhahn
On Fri, 12 Feb 2016, Evgeny Grin wrote: option is NOP for anything except W32 and AIX. Moreover, if it does matter only for W32 and AIX, let's rename it to "-w32-aix-shared-compatible". And add more flags, like "-linux-compatible", "-open-bsd-compatible". This will signal libtool that developed

Re: MSW DLLs support in libtool

2016-02-12 Thread Vadim Zeitlin
Peter Rosin lysator.liu.se> writes: > On 2016-02-11 00:38, Bob Friesenhahn wrote: > > > > Also, "-no-undefined" does not indicate if the library has undefined > > symbols (many DLLs have undefined symbols). Sorry but this is just completely incorrect as written. It's very probable that you mea

Re: MSW DLLs support in libtool

2016-02-12 Thread Vadim Zeitlin
Simon Richter hogyros.de> writes: > 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 libr

Re: MSW DLLs support in libtool

2016-02-12 Thread Peter Rosin
On 2016-02-12 22:12, Vadim Zeitlin wrote: > Several concrete questions in this thread asking for any benefits of the > current libtool behaviour went unanswered, but let me try once again > nevertheless: do you see any useful consequences of performing the check > for PIC when targeting Windows

Re: MSW DLLs support in libtool

2016-02-12 Thread Peter Rosin
On 2016-02-12 21:59, Vadim Zeitlin wrote: > Peter Rosin writes: >> On 2016-02-11 00:38, Bob Friesenhahn wrote: >>> It indicates that the build configuration has agreed to supply any >>> additional dependency libraries if there otherwise would be undefined >>> symbols. >> >> Well said, I would als

Re[2]: MSW DLLs support in libtool

2016-02-12 Thread Vadim Zeitlin
On Sat, 13 Feb 2016 00:38:15 +0100 Peter Rosin wrote: PR> On 2016-02-12 22:12, Vadim Zeitlin wrote: PR> > Several concrete questions in this thread asking for any benefits of the PR> > current libtool behaviour went unanswered, but let me try once again PR> > nevertheless: do you see any useful

Re[2]: MSW DLLs support in libtool

2016-02-12 Thread Vadim Zeitlin
On Sat, 13 Feb 2016 00:38:48 +0100 Peter Rosin wrote: PR> On 2016-02-12 21:59, Vadim Zeitlin wrote: PR> > Peter Rosin writes: PR> >> On 2016-02-11 00:38, Bob Friesenhahn wrote: PR> >>> It indicates that the build configuration has agreed to supply any PR> >>> additional dependency libraries if th