Re: cross-build problem

[Thomas Koeller]

On Sonntag, 4. November 2007, Ralf Wildenhues wrote:
> Hello Thomas,

Hi Ralf,

thanks for your quick response. However, the explanation you gave does
not quite satisfy me.

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

Why would libtool need to be aware of a sysroot being used? The linker
takes care of that. All that libtool is supposed to do is to pass my
LDFLAGS to the linker unmodified. It does so for all the 'libtool --mode=link'
commands executed during the build, and all these commands succeed. If
it did the same for '--mode=relink', that command would succeed just as
well, as I could prove by editing the command line accordingly.

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

To me this does not look like a fundamental problem, more like a
simple coding error in libtool.

thanks,
Thomas

-- 
Thomas Koeller
thomas at koeller dot dyndns dot org