Re: libtool-2.2.4 error: libtool: link: unsupported hardcode properties

[Ralf Wildenhues]

Hello Robert,

Thank you for the detailed bug report; almost perfect (see below).  :-)

* Robert Schuster wrote on Thu, Jul 10, 2008 at 10:18:01PM CEST:
> I am using libtool 2.2.4 to compile GNU Classpath and get the following
> error when compiling GNU Classpath 0.97.2:
> 
> /bin/sh ../../../i686-linux-libtool --tag=CC   --mode=link gcc -W -Wall
> -Wmissing-declarations -Wwrite-strings -Wmissing-prototypes
> -Wno-long-long -Wstrict-prototypes -pedantic -Werror
> -isystem/home/rob/oe/beagle/tmp/staging/i686-linux/usr/include -Os
> -module -version-info 0:0:0 -no-undefined
> -L/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib
> -Wl,-rpath-link,/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib
> -Wl,-rpath,/home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib -Wl,-O1 -o
> libjavanet.la -rpath
> /home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib/classpath javanet.lo
[...]
> ../../../native/jni/native-lib/libclasspathnative.la
> /home/rob/oe/beagle/tmp/staging/i686-linux/usr/lib/libmagic.la
> i686-linux-libtool: link: unsupported hardcode properties
> i686-linux-libtool: link: See the libtool documentation for more information.
> i686-linux-libtool: link: Fatal configuration error.
> 
> gcc is 4.3.1 (the one from Debian).
> 
> Incidentally this is the same problem Christian Thalinger reported a
> while back:
> 
> http://lists.gnu.org/archive/html/bug-libtool/2008-04/msg00145.html

Ahh, we don't know that yet, until we've analyzed both.

> Attached is the output of libtool --config and the compile command from
> above with --debug added (In fact it is the output of the make command).

Thanks.  In fact the 'libtool --config' is very much like the one on my
i686-linux system.  But it doesn't match your --debug output: the latter
shows that hardcode_direct is empty:

  + case $hardcode_action in
  + test '' = no

So since what your build is invoking is:
  /bin/sh ../../../i686-linux-libtool

we'd like to see the output of it (when run in the same directory):
  /bin/sh ../../../i686-linux-libtool --config

and the next step I guess would be to find out why that happens to get
those presumably strange settings during the configure stage.

Cheers,
Ralf