From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Cc: "Lock, Joshua" <joshua.lock@intel.com>
Subject: Request for branch merge
Date: Thu, 01 Apr 2010 16:33:01 +0100 [thread overview]
Message-ID: <1270135981.4993.128.camel@rex> (raw)
I've been aware that Poky and OE have been diverging slightly and I'd
like to correct this. There are some patches that I've promised for a
while too such as the rename from do_populate_staging ->
do_populate_sysroot.
With some help from Joshua Lock, I have a branch I'd like to propose be
merged into OE.dev:
http://cgit.openembedded.org/cgit.cgi/openembedded/log/?h=rpurdie/work-in-progress
This branch:
* Renames do_populate_staging -> do_populate_sysroot as per previous
staging discussion emails and also the staging directory ->
sysroots. It should convert existing builds safely and insert a
compatibility symlink. This continues the process of improving our
"staging" concept into one focused around true sysroots.
* Adds some gettext class sanity checks. In Poky this error is fatal,
for OE this is just a note for now. The idea being if AM_GNU_GETTEXT
is in configure.ac and gettext in some form isn't in DEPENDS,
something is wrong.
* Added relocatable binary processing from Poky for -native binaries
using chrpath. This isn't enabled for -cross packages due to the
relative path length problems.
* Added packaged-staging fetching capabilities. This uses new mirror
handling abilities in bitbake master branch but should work with older
bitbakes, just with less functionality.
* Started moving gcc dependency information into core gcc version
specific includes as part of the gcc cleanup.
* Converted gcc to use the new style staging
* Added EXTRA_OECONF_INITIAL and EXTRA_OECONF_INTERMEDIATE variables to
gcc as part of the gcc cleanup
* Converted binutils, modutils-cross, glibc and gdb to new style staging
* Cleaned up the gcc-cross do_install function a lot
Along with a small number of other tweaks spotted along the way.
I could post the patches individually and get Acked lines for each one
but I'm hoping to avoid that and get permission to merge the branch
directly. We have talked about most of these things in one form or
another.
Cheers,
Richard
next reply other threads:[~2010-04-01 15:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 15:33 Richard Purdie [this message]
2010-04-01 15:41 ` Request for branch merge Tom Rini
2010-04-01 15:43 ` Tom Rini
2010-04-01 16:07 ` Richard Purdie
2010-04-01 16:45 ` Tom Rini
2010-04-01 18:09 ` Richard Purdie
2010-04-01 18:33 ` Tom Rini
2010-04-01 18:43 ` Richard Purdie
2010-04-01 16:05 ` Richard Purdie
2010-04-01 16:46 ` Tom Rini
2010-04-01 15:46 ` Khem Raj
2010-04-01 16:09 ` Richard Purdie
2010-04-01 16:18 ` Andrea Adami
2010-04-01 16:29 ` Richard Purdie
2010-04-01 16:37 ` Gary Thomas
2010-04-01 17:17 ` Joshua Lock
2010-04-01 17:55 ` Koen Kooi
2010-04-01 18:17 ` Richard Purdie
2010-04-01 20:03 ` Chris Larson
2010-04-01 20:34 ` Tom Rini
2010-04-01 21:08 ` Koen Kooi
2010-04-01 21:25 ` Tom Rini
2010-04-01 21:27 ` Philip Balister
2010-04-01 22:26 ` Tom Rini
2010-04-02 13:40 ` Koen Kooi
2010-04-02 14:35 ` Koen Kooi
2010-04-02 21:41 ` Richard Purdie
2010-04-03 7:21 ` Koen Kooi
2010-04-02 21:29 ` Richard Purdie
2010-04-03 7:23 ` Koen Kooi
2010-04-08 15:40 ` Joshua Lock
2010-04-03 13:24 ` Koen Kooi
2010-04-12 8:37 ` Koen Kooi
2010-04-12 15:59 ` Tom Rini
2010-04-12 16:46 ` Joshua Lock
2010-05-01 23:29 ` Richard Purdie
2010-05-03 16:46 ` Tom Rini
2010-05-04 18:10 ` Richard Purdie
2010-05-04 18:55 ` Tom Rini
2010-05-05 23:22 ` Richard Purdie
2010-05-05 23:30 ` Tom Rini
2010-04-12 16:45 ` Joshua Lock
2010-04-12 17:47 ` Koen Kooi
2010-04-12 20:55 ` Koen Kooi
2010-04-12 22:19 ` Koen Kooi
2010-04-13 3:46 ` Richard Purdie
2010-04-13 7:06 ` Koen Kooi
2010-05-01 23:28 ` Richard Purdie
2010-05-02 14:13 ` Koen Kooi
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=1270135981.4993.128.camel@rex \
--to=rpurdie@rpsys.net \
--cc=joshua.lock@intel.com \
--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.