All of lore.kernel.org
 help / color / mirror / Atom feed
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 18:28:14 +0100	[thread overview]
Message-ID: <1279906094.13006.60.camel@rex> (raw)
In-Reply-To: <1279882577.13006.40.camel@rex>

On Fri, 2010-07-23 at 11:56 +0100, Richard Purdie wrote:
> I'm testing some patches against poky which add an extra directory level
> in /usr/bin/. I've also patched binutils-cross to stop spewing excess
> bits all over the place. I'll report back how it goes.

I got things fixed in Poky, pending more extensive testing which I
haven't had time for yet. There are several things needed though:


a) Have gcc dump a load of symlinks into its libexec directory:

http://git.pokylinux.org/cgit.cgi/poky/commit/?id=bf8023237c6fe43781fa4ce0db00f2b08cab7817

This is so when it tries to find "as" (not TARGET_PREFIX-as) it will
find the right ones. It means we don't need the duplicates from bintuils
which always end up in a multimachine unsafe path which means we can
then:

b) Kill off bits of binutils that don't make sense

http://git.pokylinux.org/cgit.cgi/poky/commit/?id=066535608e879c0327dfa874f3978d6cc15fa59f

and then 

c) Create some extra path layers which hold the different toolchains. We
have to split out bindir, libdir and libexec dir as they all contain
varying amounts of potentially machine sensitive code (sysroot
settings).

http://git.pokylinux.org/cgit.cgi/poky/commit/?id=66d7b58f224e55b70b80a01d451270b7de757885


Poky has the complication its using gcc-runtime which builds/packages
the target gcc libs separately where it possibly can. I had to tweak
things to account for this with some other patches and also make that
multi arch safe. I think OE should be ok in this regard but something
like:

http://git.pokylinux.org/cgit.cgi/poky/commit/?id=ab82312433f8a7eacd6ee90d3bc9e5153282ec3f

may be required due to the way gcc makes assumptions about paths.

Cheers,

Richard




  reply	other threads:[~2010-07-23 17:29 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
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 [this message]
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=1279906094.13006.60.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.