[ This is a Libtool bug. It is better discussed on the bug-libtool
mailing list. I am Cc'ing that list. Please remove the autoconf
list from further resposes, thankyou. ]
* Ray Lehtiniemi wrote on Tue, Jan 11, 2005 at 08:52:47PM CET:
>
> i am having difficulty with my cross-development setup. i am
> using:
>
> crosstool-0.28-rc37 (i686-linux targetting arm-linux)
> automake (GNU automake) 1.8.3
> autoconf (GNU Autoconf) 2.59
> ltmain.sh (GNU libtool) 1.5.2 (1.1220.2.60 2004/01/25 12:25:08)
Please consider updating to a more recent Libtool.
It will not solve your problem, though.
Libtool does not yet support cross-compiling very well. We would
like to change that, though. You can help by answering the following:
> DESTDIR=/tmp/XXX
> PREFIX=/home/foo
>
*snip*
> if i then configure the prog2 package with '--with-prog1=${DESTDIR}/${PREFIX}',
> the build works, and my executable gets installed into $DESTDIR/bin.
>
> however, the final executable has this:
>
> # armv5b-softfloat-linux-objdump -p /tmp/XXX/home/foo/bin/prog2
>
> Dynamic Section:
> NEEDED libprog1.so.0
> NEEDED libc.so.6
> RPATH /tmp/XXX//home/foo/lib
>
>
> it seems to me that this RPATH entry in the final executable should
> be "RPATH /home/foo/lib", no? how do i get rid of the DESTDIR in my
> RPATH? how do i tell configure that libprog1.la just happens to be
> sitting in DESTDIR at the moment, so build against PREFIX, not
> DESTDIR/PREFIX?
Please include the link line of prog2 as well as its output with --debug
added as Libtool option.
If uninstalled prog2 is a libtool wrapper script, show the contents of
relink_command within that script, and the output of executing the
relink with --debug added as Libtool option.
Consider packed (gzip or bzip2) attachments for long output.
Regards,
Ralf
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
