Based on the debug output I changed the names of the Boost dll's from
boost_xxx.dll to libboost_xxx.dll and the warning went away.
I was under the impression that the search order for libraries was:
libxxx.dll.a
xxx.dll.a
libxxx.a
libxxx.dll
xxx.dll
Apparently it is not so.
This trick did NOT wo
On Tue, 2010-08-24 at 18:53 +0200, Ralf Wildenhues wrote:
> If 2.2.10 is still not working right, please post the output of
> the failing 'libtool --mode=link' command, with --debug added as
> first argument after libtool. Thank you.
I am sorry to say but it fails. Attached the output from the co
On Tue, 2010-08-24 at 18:53 +0200, Ralf Wildenhues wrote:
> Which ./libtool --version is your package using? With 2.2.10,
> no hacks should be necessary.
>
> If 2.2.10 is still not working right, please post the output of
> the failing 'libtool --mode=link' command, with --debug added as
> first
Hello,
* Eric Blake wrote on Tue, Aug 24, 2010 at 06:47:51PM CEST:
> On 08/24/2010 10:42 AM, Joost Kraaijeveld wrote:
> >*** Since this library must not contain undefined symbols,
> >*** because either the platform does not support them or
> >*** it was explicitly requested with -no-undefined,
> >
[adding libtool]
On 08/24/2010 10:42 AM, Joost Kraaijeveld wrote:
*** Since this library must not contain undefined symbols,
*** because either the platform does not support them or
*** it was explicitly requested with -no-undefined,
*** libtool will only create a static version of it.
It seems
