[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cross-build problem
From: |
Ralf Wildenhues |
Subject: |
Re: cross-build problem |
Date: |
Sun, 4 Nov 2007 14:04:49 +0100 |
User-agent: |
Mutt/1.5.17 (2007-11-02) |
Hello Thomas,
* Thomas Koeller wrote on Sun, Nov 04, 2007 at 01:48:43PM CET:
>
> I am encountering problems using libtool-1.5.24 in a cross-build
> environment (build system x86_64-pc-linux-gnu, target mips-linux-gnu).
> I am trying to build the Linux-PAM-0.99.8.1 package. Building works
> fine, but --mode=install fails.
>
> Because I am cross-building, my CFLAGS and LDFLAGS variables contain
> the --sysroot switch. When 'libtool --mode=install' is invoked, the
> following happens:
Instead of passing --sysroot, you can try passing -Wc,--sysroot=... to
get the flag through libtool. It may work for you, but it will not
solve the more fundamental underlying issue: Libtool does not recognize
that you are using a sysroot, and it will either search for dependent
installed libraries in the wrong locations or put the wrong (sysroot-
prefixed) deplib paths into the .la file that you are creating.
This is a limitation in libtool that has not been solved yet. One way
to work around it is to use -Wc, as above, and afterwards rewrite
dependency_libs in the .la file you just created.
Note that this does not address the issue of indirect deplibs of
installed libraries below the sysroot: if they contain run paths
that will only be valid once the libs are in their final place,
things can still fail because the link editor won't find them.
(Shouldn't happen in your case as /usr/lib libraries typically
don't get run paths added.)
Hope that helps.
Cheers,
Ralf