From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/4][RFC] Remove CROSS_DIR, install cross-packages into native sysroot
Date: Fri, 23 Jul 2010 09:59:08 +0100 [thread overview]
Message-ID: <1279875548.13006.32.camel@rex> (raw)
In-Reply-To: <i2bir6$un3$1@dough.gmane.org>
On Fri, 2010-07-23 at 10:11 +0200, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 23-07-10 10:02, Phil Blundell wrote:
> > On Fri, 2010-07-23 at 09:25 +0200, Koen Kooi wrote:
> >> There is a BIG problem with these patches, they break multimachine builds.
> >>
> >> The previous situation had:
> >>
> >> cross/armv7a-angstrom-foo/usr/bin/
> >> cross/armv5te-angstrom-foo/usr/bin/
> >> etc
> >>
> >> The new situation has:
> >>
> >> x86_64-linux/usr/bin
> >>
> >> So all the toolchains get dropped into the *same* directory, which
> >> breaks horribly.
> >
> > Which are the actual binaries that collide? I would have thought that
> > everything which gets installed into the cross bindir ought to be
> > prefixed with TARGET_SYS (i.e. usr/bin/armv7a-angstrom-linux-gcc, etc).
>
> It's all 'arm-angstrom-foo', I was just about to make the suggestion to
> change it to 'armv7a-angstrom-foo' :)
I've just been talking to Koen about this. When building for armv7a,
TARGET_ARCH which goes into TARGET_PREFIX and TARGET_SYS is "arm".
I suspect if we change TARGET_ARCH to be armv7a, nasty things will
happen but I could be wrong.
If that doesn't help which I suspect it won't, my gut instinct is to add
a architecture specific directory under bin for the cross bits. This
could be as simple as changing bindir in cross.bbclass.
> I don't know if that solves the binutils-cross problem[1], though.
>
> Koen
>
> [1] http://thread.gmane.org/gmane.comp.handhelds.openembedded/34685
Is that libiberty.a file actually useful or could we just stop
binutils-cross installing it?
Cheers,
Richard
next prev parent reply other threads:[~2010-07-23 8:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 18:04 [PATCH 0/4][RFC] Remove CROSS_DIR, install cross-packages into native sysroot Khem Raj
2010-07-21 18:04 ` [PATCH 1/4] classes, bitbake.conf: " Khem Raj
2010-07-21 21:52 ` Tom Rini
2010-07-21 18:04 ` [PATCH 2/4] toolchain: Remove references to CROSS_DIR Khem Raj
2010-07-21 21:52 ` Tom Rini
2010-07-21 18:04 ` [PATCH 3/4] recipes: Fix " Khem Raj
2010-07-21 21:53 ` Tom Rini
2010-07-21 18:04 ` [PATCH 4/4] sanity.bbclass, abi_version.conf: Bump the ABI to inform that cross has died Khem Raj
2010-07-21 21:53 ` Tom Rini
2010-07-21 21:52 ` [PATCH 0/4][RFC] Remove CROSS_DIR, install cross-packages into native sysroot Tom Rini
2010-07-22 8:27 ` Richard Purdie
2010-07-22 14:02 ` Chris Larson
2010-07-22 14:24 ` Martin Jansa
2010-07-22 14:54 ` Koen Kooi
2010-07-23 7:25 ` Koen Kooi
2010-07-23 8:02 ` Phil Blundell
2010-07-23 8:11 ` Koen Kooi
2010-07-23 8:59 ` Richard Purdie [this message]
2010-07-23 9:18 ` Frans Meulenbroeks
2010-07-23 17:20 ` Khem Raj
2010-07-23 17:30 ` Chris Larson
2010-07-23 17:41 ` Khem Raj
2010-07-23 20:44 ` Khem Raj
2010-07-24 2:31 ` Khem Raj
2010-07-23 9:35 ` Esben Haabendal
2010-07-23 10:08 ` Koen Kooi
2010-07-23 10:23 ` Phil Blundell
2010-07-23 11:24 ` Richard Purdie
2010-07-23 11:46 ` Esben Haabendal
2010-07-23 17:12 ` Khem Raj
2010-07-23 10:17 ` Phil Blundell
2010-07-23 10:56 ` Richard Purdie
2010-07-23 17:28 ` Richard Purdie
2010-07-23 17:14 ` Khem Raj
2010-07-23 8:18 ` Martin Jansa
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=1279875548.13006.32.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox