Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: binutils-cross problem with multimachine config after cross changes
Date: Fri, 23 Jul 2010 10:52:18 +0200	[thread overview]
Message-ID: <i2bl83$7im$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTim=jp4BQTg_nPkMg2yN_-g-6_Stta6ZkjD3H-Xb@mail.gmail.com>

-----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-----




  reply	other threads:[~2010-07-23  8:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23  7:10 binutils-cross problem with multimachine config after cross changes Koen Kooi
2010-07-23  8:36 ` Frans Meulenbroeks
2010-07-23  8:52   ` Koen Kooi [this message]
2010-07-23 17:02 ` Khem Raj
2010-07-23 17:38   ` Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='i2bl83$7im$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox