linking with libtool and link_all_deplibs
dilyan.palauzov at aegee.org
Mon Jul 16 03:23:46 EDT 2012
I reverted the change. On my system (libtool 2.4.2) link_all_deplibs
On 16.07.2012 02:30, Greg Banks wrote:
> On Sun, Jul 15, 2012, at 12:26 PM, Дилян Палаузов wrote:
>> I reverted the changes causing the warnings with static in the header
>> The linking problem, Bron mentioned on 12.07., was is caused by
>> (./libtool --config)'s link_all_deplibs=no .
>> Does anybody have an idea, when is link_all_deplibs set to no, and when
>> to yes/unknown?
> On my machine it's set in configure
> 8957 link_all_deplibs=unknown
> 8980 case $host_os in
> 8996 linux* | k*bsd*-gnu)
> 8997 link_all_deplibs=no
> 8998 ;;
> 8999 esac
> This is with autoconf 2.67, automake 1.11.1 libtool 2.2.6b.
> Looking at the configure code, it's set to 'yes' on those platforms
> where the dynamic linker is incapable of, or due to bugs intermittently
> capable of, transitively following library dependencies on other
> libraries at program link time. In other words, the correct value for
> all Linux variants is 'no'.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 380 bytes
Desc: not available
Url : http://lists.andrew.cmu.edu/pipermail/cyrus-devel/attachments/20120716/612a7e86/attachment.vcf
More information about the Cyrus-devel