[PATCH] Get library installation path for target architecture

Rob Landley rob at landley.net
Fri Mar 24 03:30:38 UTC 2006


On Thursday 23 March 2006 10:20 pm, Mike Frysinger wrote:
> On Thursday 23 March 2006 21:43, Rob Landley wrote:
> > On Thursday 23 March 2006 5:12 pm, Pavel Roskin wrote:
> > > applets/install.sh uses uname to determine where to install the
> > > libraries.  So, cross-compiling on x86_64 to arm would install
> > > libbusybox to /lib64.
> >
> > Good point.
> >
> > Applied.
>
> except that the proposed fix doesnt work when using a multilib compiler
>
> so building on an amd64 machine targeting a x86 using the native gcc
> compiler will still install into the wrong location

A) So we have to feed in whatever the target flag is to gcc in order to get it 
to spit out the right path?

B) Did that work before?

The situation I'm actually wondering about is a cross-compile where during the 
build the libraries live 
at /opt/totally/ludicrous/deep/path/to/cross/compiler and then on the target 
system they live in "/lib".  Will that do the right thing?

> -mike

Rob
-- 
Never bet against the cheap plastic solution.



More information about the busybox mailing list