adding custom CFLAGS

Denis Vlasenko vda.linux at googlemail.com
Thu Oct 19 19:21:00 UTC 2006


On Wednesday 18 October 2006 22:22, Larry Brigman wrote:
> On 10/18/06, Dave Hylands <dhylands at gmail.com> wrote:
> > Hi Larry,
> >
> > > Is it normal for a cross-compiled version(586-gcc) of busybox to
> > > search 686 dirs?
> > ...snip...
> > > open("/etc/ld.so.cache", O_RDONLY)      = -1 ENOENT (No such file or directory)
> > > open("/lib/tls/i686/sse2/libcrypt.so.1", O_RDONLY) = -1 ENOENT (No
> >
> > So it seems that you're running your 586 cross-compiled busybox in
> > your 686 environment, so yeah it will access 686 stuff since it's
> > referencing /etc/ld.so.cache which will contain pointers to 686 files.
> 
> running it in a qemu box.  The file system doesn't have a ld.so.cache
> or ld.so.preload
> Do I need to create one?
> 
> If the make system was using my environment variables that pointed to
> my toolchain
> I don't think I would be getting this.

I compile my gcc, glibc, binutils etc for 486, yet still I see
a lot of ...686... in strace, every time. I am pretty sure
glibc dynamic loader is doing this. It tries to use "most CPU-optimized libs"
first.
--
vda



More information about the busybox mailing list