binutils-cross problem with multimachine config after cross changes

binutils-cross problem with multimachine config after cross changes

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I was doing a multimachine build and the armv7a bits completed
beautifully, but the armv5te bits break in binutils-cross:

| /usr/bin/ld:
/work/autobuilder/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/lib/libiberty.a(cplus-dem.o):
relocation R_X86_64_32
used when making a shared object; recompile with -fPIC
|
/work/autobuilder/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/lib/libiberty.a:
could not read symbols: Bad value
| collect2: ld returned 1 exit status

Does anyone have a quick fix for that? My tinderbox looks so said with
all that red :(

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMSUBLMkyGM64RGpERAgopAJ96q9OiWD8Eywv0L/09b8wP92QfnwCgpt11
EoOVgGxVY+MeWMPJcoF8pg8=
=1cA2
-----END PGP SIGNATURE-----

Re: binutils-cross problem with multimachine config after cross changes

[Frans Meulenbroeks]

2010/7/23 Koen Kooi <k.kooi@student.utwente.nl>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I was doing a multimachine build and the armv7a bits completed
> beautifully, but the armv5te bits break in binutils-cross:
>
> | /usr/bin/ld:
>
> /work/autobuilder/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/lib/libiberty.a(cplus-dem.o):
> relocation R_X86_64_32
> used when making a shared object; recompile with -fPIC
> |
>
> /work/autobuilder/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/lib/libiberty.a:
> could not read symbols: Bad value
> | collect2: ld returned 1 exit status
>
> Does anyone have a quick fix for that? My tinderbox looks so said with
> all that red :(
>

Yesterday I noticed a similar issue with binutils 2.20.1 for nios2 when ld
was called with -shared.
2.17.50 did not have the problem.
Didn't have time to investigate yet. (and probably it'll take a day or two
before I get to this)

Are you using the same version of binutils for v5 and v7? (and which one).

Frans

>
> regards,
>
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFMSUBLMkyGM64RGpERAgopAJ96q9OiWD8Eywv0L/09b8wP92QfnwCgpt11
> EoOVgGxVY+MeWMPJcoF8pg8=
> =1cA2
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: binutils-cross problem with multimachine config after cross changes

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 23-07-10 10:36, Frans Meulenbroeks wrote:
> 2010/7/23 Koen Kooi <k.kooi@student.utwente.nl>
> 
> Hi,
> 
> I was doing a multimachine build and the armv7a bits completed
> beautifully, but the armv5te bits break in binutils-cross:
> 
> | /usr/bin/ld:
> 
> /work/autobuilder/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/lib/libiberty.a(cplus-dem.o):
> relocation R_X86_64_32
> used when making a shared object; recompile with -fPIC
> |
> 
> /work/autobuilder/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/lib/libiberty.a:
> could not read symbols: Bad value
> | collect2: ld returned 1 exit status
> 
> Does anyone have a quick fix for that? My tinderbox looks so said with
> all that red :(
> 
> 
>> Yesterday I noticed a similar issue with binutils 2.20.1 for nios2 when ld
>> was called with -shared.
>> 2.17.50 did not have the problem.
>> Didn't have time to investigate yet. (and probably it'll take a day or two
>> before I get to this)

I suspect the second binutils-cross is trying to link with the libs from
the first, which breaks.

>> Are you using the same version of binutils for v5 and v7? (and which one).

ANGSTROM_BINUTILS_VERSION                ?= "2.18"
ANGSTROM_BINUTILS_VERSION_armv4          ?= "2.20"
ANGSTROM_BINUTILS_VERSION_armv7a         ?= "2.18.50.0.7"

Angstrom-next has a saner layout, that used 2.20.x for everything, but
lots of things don't build with that and among those things are the
things that bring in my paycheck.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMSVhCMkyGM64RGpERApymAJ0Yh8zUt3DklFUjAHc1P40t03LwAQCcCxDK
6LJ5tQ/Vb7auH78ldPINVJE=
=S65W
-----END PGP SIGNATURE-----

Re: binutils-cross problem with multimachine config after cross changes

[Khem Raj]

On Fri, Jul 23, 2010 at 12:10 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I was doing a multimachine build and the armv7a bits completed
> beautifully, but the armv5te bits break in binutils-cross:
>
> | /usr/bin/ld:
> /work/autobuilder/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/lib/libiberty.a(cplus-dem.o):
> relocation R_X86_64_32
> used when making a shared object; recompile with -fPIC
> |
> /work/autobuilder/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/lib/libiberty.a:
> could not read symbols: Bad value
> | collect2: ld returned 1 exit status

interesting. Does your native sysroot also have
sysroots/x86_64-linux/usr/lib/libiberty_pic.a ?
if not then its a problem. but that said I think different versions
for different machines of same arch
is not going to work if they share same canonical names for tools. For
different architectures it will work.

You can try to remove

>
> Does anyone have a quick fix for that? My tinderbox looks so said with
> all that red :(
>
> regards,
>
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFMSUBLMkyGM64RGpERAgopAJ96q9OiWD8Eywv0L/09b8wP92QfnwCgpt11
> EoOVgGxVY+MeWMPJcoF8pg8=
> =1cA2
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: binutils-cross problem with multimachine config after cross changes

[Richard Purdie]

On Fri, 2010-07-23 at 10:02 -0700, Khem Raj wrote:
> On Fri, Jul 23, 2010 at 12:10 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> > I was doing a multimachine build and the armv7a bits completed
> > beautifully, but the armv5te bits break in binutils-cross:
> >
> > | /usr/bin/ld:
> > /work/autobuilder/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/lib/libiberty.a(cplus-dem.o):
> > relocation R_X86_64_32
> > used when making a shared object; recompile with -fPIC
> > |
> > /work/autobuilder/build/tmp-angstrom_2008_1/sysroots/x86_64-linux/usr/lib/libiberty.a:
> > could not read symbols: Bad value
> > | collect2: ld returned 1 exit status
> 
> interesting. Does your native sysroot also have
> sysroots/x86_64-linux/usr/lib/libiberty_pic.a ?
> if not then its a problem. but that said I think different versions
> for different machines of same arch
> is not going to work if they share same canonical names for tools. For
> different architectures it will work.
> 
> You can try to remove

I'm removing this in poky and will also look to remove the ones
generated by gcc. If we need this file it should be being build by a
bintutils-native (or libnfd-native)...

Cheers,

Richard