From: Khem Raj <raj.khem@gmail.com>
To: OE core <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/2] Fixes for eglibc parallel build and elfutils on uclibc
Date: Tue, 24 May 2011 12:18:45 -0700 [thread overview]
Message-ID: <cover.1306264437.git.raj.khem@gmail.com> (raw)
This patchset addresses the issue Saul ran into with do_install on eglibc
second patch is to get elfutils compile partially for uclibc, the reason is that
it also provides libelf which is needed by other packages such as gcc 4.5
to build. So either we add a new recipe for just providing libelf and add
magic to chose which one to use or we make elfutils to not build everything
but only elfutils when doing it for uclibc. I chose the second aproach
The following changes since commit d33ada10fdcc830f11dc47bd55f529157d1d280b:
elfutils_0.148.bb: Fix compilation on uclibc (2011-05-24 12:06:30 -0700)
are available in the git repository at:
git@git.openembedded.org:openembedded-core-contrib.git kraj/misc-fixes
http://cgit.openembedded.org/cgit.cgi//log/?h=kraj/misc-fixes
Khem Raj (2):
elfutils_0.148.bb: Fix compilation on uclibc
eglibc.inc: Transfer PARALLEL_MAKE to PARALLELMFLAGS
meta/recipes-core/eglibc/eglibc.inc | 6 ++
.../elfutils/elfutils-0.148/uclibc-support.patch | 91 ++++++++++++++++++++
meta/recipes-devtools/elfutils/elfutils_0.148.bb | 15 +++-
3 files changed, 109 insertions(+), 3 deletions(-)
create mode 100644 meta/recipes-devtools/elfutils/elfutils-0.148/uclibc-support.patch
--
1.7.4.1
next reply other threads:[~2011-05-24 19:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 19:18 Khem Raj [this message]
2011-05-24 19:18 ` [PATCH 1/2] elfutils_0.148.bb: Fix compilation on uclibc Khem Raj
2011-05-24 19:18 ` [PATCH V2 2/2] eglibc.inc: Transfer PARALLEL_MAKE to PARALLELMFLAGS Khem Raj
2011-05-24 20:41 ` Khem Raj
2011-05-25 17:21 ` [PATCH 0/2] Fixes for eglibc parallel build and elfutils on uclibc Saul Wold
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=cover.1306264437.git.raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@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