[gentoo-embedded] binutils-config-1.9-r1 causes armeb-softfloat-linux-uclibc to miscompile packages

[gentoo-embedded] binutils-config-1.9-r1 causes armeb-softfloat-linux-uclibc to miscompile packages

[Derick Swanepoel]

I finally got my armeb-softfloat-linux-uclibc toolchain to compile
busybox, etc. without the dreaded "can't resolve symbol '__udivsi3'"
problems, but only with binutils-config-1.8-r7. Now that cross
compiling forces at least binutils-config-1.9-r1, my toolchain once
again produces broken binaries.

I'm not sure if this has anything to do with the move of
cross-toolchain binaries from /usr/CTARGET/*bin to
/usr/CHOST/CTARGET/*bin/.

I have found that I can avoid the "can't resolve symbol '__udivsi3'"
problems by linking binaries statically, so I'm guessing this issue
has something to do with dynamic linking. The problem lies in the
binaries themselves, however, since uClibc has remained identical
after upgrading binutils.

Is there anyone else who actually has a working
armeb-softfloat-linux-uclibc toolchain?

Derick
-- 
gentoo-embedded@gentoo.org mailing list

Re: [gentoo-embedded] binutils-config-1.9-r1 causes armeb-softfloat-linux-uclibc to miscompile packages

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 401 bytes --]

On Thursday 14 September 2006 10:56, Derick Swanepoel wrote:
> I finally got my armeb-softfloat-linux-uclibc toolchain to compile
> busybox, etc. without the dreaded "can't resolve symbol '__udivsi3'"
> problems, but only with binutils-config-1.8-r7. Now that cross
> compiling forces at least binutils-config-1.9-r1, my toolchain once
> again produces broken binaries.

are you using gcc-4.1 ?
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

Re: [gentoo-embedded] binutils-config-1.9-r1 causes armeb-softfloat-linux-uclibc to miscompile packages

[Derick Swanepoel]

On 14/09/06, Mike Frysinger <vapier@gentoo.org> wrote:
> On Thursday 14 September 2006 10:56, Derick Swanepoel wrote:
> > I finally got my armeb-softfloat-linux-uclibc toolchain to compile
> > busybox, etc. without the dreaded "can't resolve symbol '__udivsi3'"
> > problems, but only with binutils-config-1.8-r7. Now that cross
> > compiling forces at least binutils-config-1.9-r1, my toolchain once
> > again produces broken binaries.
>
> are you using gcc-4.1 ?
> -mike

My host environment's compiler is gcc-4.1.1, but the cross-compiler is
gcc-3.4.6-r2.

Derick
-- 
gentoo-embedded@gentoo.org mailing list