* Alon Bar-Lev <alonbl@gentoo.org> schrieb:
> Hello,
>
> I have an issue with libtool and cross compile.

libtool is totally broken and unable to cross-compile.
you might consider unitool (and it's libtool-replacement).


cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service - http://www.metux.de/
---------------------------------------------------------------------
Please visit the OpenSource QM Taskforce:
http://wiki.metux.de/public/OpenSource_QM_Taskforce
Patches / Fixes for a lot dozens of packages in dozens of versions:
http://patches.metux.de/
---------------------------------------------------------------------
--
gentoo-embedded@gentoo.org mailing list

On Friday 23 November 2007, Alon Bar-Lev wrote:
> I have an issue with libtool and cross compile.

as much of a tool as Enrico is, he is right that libtool is not currently
conducive to cross-compiling. pkg-config seems to be doing a nicer job of
exporting dependencies.

> When merging a library which uses libtool, it creates the .la file
> with libdir= variable, usually it will contain /usr/lib.

libtool is based off of $libdir (which is usually based off of $prefix). it
doesnt really have a concept of separating build and run paths.

> Eventually I ended up with patching every package I use with the
> following patch in order to make it work:

a nicer method would probably to add a post-install bashrc hook that mungs the
installed libtool scripts (*.la) by changing libdir= by prefixing $SYSROOT.
ive used this in other environments pretty successfully.

sed -i -e "/^libdir=/s:=:='$SYSROOT':" $SYSROOT/usr/lib*/*.la
-mike

Thanks for the reply!

On 12/24/07, Mike Frysinger <vapier@gentoo.org> wrote:
> a nicer method would probably to add a post-install bashrc hook that mungs the
> installed libtool scripts (*.la) by changing libdir= by prefixing $SYSROOT.
> ive used this in other environments pretty successfully.
>
> sed -i -e "/^libdir=/s:=:='$SYSROOT':" $SYSROOT/usr/lib*/*.la

This is what I've done... As a temporary solution...
But it breaks the chroot environment...
I think better is to fix libtool in elibtoolize, so that it will
append ${ROOT} to the libdir when reading the .la files.

Best Regards,
Alon Bar-Lev.
--
gentoo-embedded@gentoo.org mailing list

On Tuesday 25 December 2007, Alon Bar-Lev wrote:
> On 12/24/07, Mike Frysinger <vapier@gentoo.org> wrote:
> > a nicer method would probably to add a post-install bashrc hook that
> > mungs the installed libtool scripts (*.la) by changing libdir= by
> > prefixing $SYSROOT. ive used this in other environments pretty
> > successfully.
> >
> > sed -i -e "/^libdir=/s:=:='$SYSROOT':" $SYSROOT/usr/lib*/*.la
>
> This is what I've done... As a temporary solution...
> But it breaks the chroot environment...

*shrug* most people do not use the development root as the runtime
environment, let alone do building on the embedded machine. so such an issue
isnt a big deal.

> I think better is to fix libtool in elibtoolize, so that it will
> append ${ROOT} to the libdir when reading the .la files.

you mean prepend. feel free to write such a patch. then again, that too is
not a solution as $(ROOT) is merely where things get installed ... you cannot
assume it is the place to link against things. it is not the sysroot.
-mike