Re: bug in libtool rpath setting for _LT_AC_TAGVAR(hardcode_libdir_flag_spec, $1) (libtool 1.5.22)

[Ralf Wildenhues]

Hello James,

Thanks for the report.

* James Andrewartha wrote on Wed, Dec 13, 2006 at 12:53:32AM CET:
> 
> The stable libtool release has a bug in libtool.m4 that sets 
> _LT_AC_TAGVAR(hardcode_libdir_flag_spec, $1) to '${wl}--rpath ${wl}$libdir'
> by default instead of '${wl}-rpath ${wl}$libdir' (one less -). This causes 
> the build failure seen at 
> http://jhbuild.bxlug.be/builds/2006-12-12-0005/logs/evolution-data-server/#build
> 
> This was fixed in the development release two years ago:

Yes, but we never knew or thought it was a necessity, we fixed it for
consistency only, thinking that ld accepts both -rpath and --rpath:
<http://lists.gnu.org/archive/html/libtool-patches/2004-11/msg00039.html>

And if you look closer at the build log, you'll find earlier link
command lines that succeed with --rpath.  So the failure is of a
different nature, but it does look like it could be a libtool bug.
Where are libnss3.so, libsmime3.so, libssl3.so, and libsoftokn3.so
located?  Could you rerun 'make' non-parallel so we see which link
is actually failing?

Could you post
  ./libtool --config

for the libtool script generated by the build, from the
/scratch/gnometinderbox/jhautobuild/cvs/evolution-data-server directory?

Also interesting would be (bzip2'ed) log of

  cd /scratch/gnometinderbox/jhautobuild/cvs/evolution-data-server/camel
  rm libcamel-1.2.la
  make libcamel-1.2.la LIBTOOL='../libtool --debug'

and similar for the link that is actually failing.

Thanks,
Ralf