On Thu, 24 May 2012 07:47:04 -0400 Andrew Bradford <[email protected]> wrote:
> On Thu, 24 May 2012 00:49:46 -0500 > DJ Lucas <[email protected]> wrote: > > > I suspect you are looking > > for LD_LIBRARY_PATH...at least that's what works on native compilers, > > though I suspect the same with cross compilers since it runs native, > > just the output is for different arch. If my guess is right, you'll want > > something like the following in your working environment: > > For example, output from my armel GCC shows where it expects includes > and libs: > > andrew@bradford:~/calc/linux$ arm-linux-gnueabi-gcc -v > Target: arm-linux-gnueabi > Configured with: <snip> > --libdir=/usr/lib --includedir=/usr/arm-linux-gnueabi/include > --build=x86_64-linux-gnu --host=x86_64-linux-gnu > --target=arm-linux-gnueabi --with-headers=/usr/arm-linux-gnueabi/include > --with-libs=/usr/arm-linux-gnueabi/lib OK, so that output isn't where gcc searches for things. It's just the info provided when gcc was configured and built. The actual search path can be different. Better switches to see where gcc looks for things is '-print-search-dirs' which will show you where gcc will look. -Andrew _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org
