[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cross-compiling, RPATH, and DESTDIR vs. AC_ARG_WITH

From: Ray Lehtiniemi
Subject: Re: cross-compiling, RPATH, and DESTDIR vs. AC_ARG_WITH
Date: Sat, 22 Jan 2005 15:14:42 -0700
User-agent: Mutt/1.5.6i

On Sat, Jan 22, 2005 at 09:49:14AM +0100, Ralf Wildenhues wrote:
> * Ray Lehtiniemi wrote on Tue, Jan 11, 2005 at 08:52:47PM CET:
> Please consider updating to a more recent Libtool.
> It will not solve your problem, though.

for cross-compiling, is it recommended to follow the 1.5 series or
the 1.9 series? (or 2.1?)

> Libtool does not yet support cross-compiling very well.  We would
> like to change that, though.

i've got a few cross-projects for which i was hoping to rely upon
libtool, so i'm interested in filing bug reports and following up on

i don't see a bugzilla on the home page... is this mailing list the
primary vehicle for tracking issues?

> 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.

i don't normally run libtool explicitly... i just run autoreconf,
configure, and make...  how and where would i invoke libtool directly
to produce this output?

instead, i have pared down my example to a minimal testcase and
attached a gzipped tarball for you to examine.  it turns out cross-compiling
isn't a factor, and the bug shows itself even on a native build, so
it should be fairly easy to reproduce on your end.

please extract the attached tarball and have a look at the 'RUNME'
script in the top level dir.   that's the minimal test case i could
come up with to exhibit the faulty RPATH.


     Ray L   <address@hidden>

Attachment: lt-bug.tar.gz
Description: application/gunzip

reply via email to

[Prev in Thread] Current Thread [Next in Thread]