From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: binutils-cross problem with multimachine config after cross changes
Date: Fri, 23 Jul 2010 18:38:32 +0100 [thread overview]
Message-ID: <1279906712.13006.62.camel@rex> (raw)
In-Reply-To: <AANLkTi=HD8OXhMhyaXHLfGsOYESC4+1s5fBYjCZFzsUm@mail.gmail.com>
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
prev parent reply other threads:[~2010-07-23 17:39 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
2010-07-23 17:02 ` Khem Raj
2010-07-23 17:38 ` Richard Purdie [this message]
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=1279906712.13006.62.camel@rex \
--to=rpurdie@rpsys.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.