adding custom CFLAGS

Larry Brigman larry.brigman at gmail.com
Thu Oct 19 00:20:33 UTC 2006


On 10/18/06, Dave Hylands <dhylands at gmail.com> wrote:
> Hi Larry,
>
> > > 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.
>
> Hmm. What does running ldd report on your executable. It should list
> the shared libraries that it was compiled to use.
>
> For example, mine reports:
> # ldd busybox
>         libcrypt.so.0 => /lib/libcrypt.so.0 (0x40012000)
>         libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x4002e000)
>         libc.so.0 => /lib/libc.so.0 (0x4003f000)
>         ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x40000000)
>

# ldd /bin/busybox
        linux-gate.so.1 =>  (0xffffe000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7fbe000)
        libm.so.6 => /lib/libm.so.6 (0xb7fb8000)
        libc.so.6 => /lib/libc.so.6 (0xb7efb000)
        /lib/ld-linux.so.2 (0xb7fec000)

I am starting to suspect my toolchain libraries were built by gcc on a
686 processor
with something like -mtune=i686.  I didn't build the libraries or the toolchain
(vendor provided).



More information about the busybox mailing list