From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/7] Prelink/ld bug and rpm compilation on uclibc
Date: Mon, 4 Jun 2012 15:21:29 -0700 [thread overview]
Message-ID: <cover.1338848379.git.raj.khem@gmail.com> (raw)
This patch fixes bunch of recipes to build on uclibc
binutils patch fixes the prelink problem recently seen on powerpc
The following changes since commit e3113827810e98eb1b012f0b280fb917199704c1:
webkit-gtk: Use glib as unicode backend to avoid browser crash (2012-05-30 17:37:58 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib kraj/misc-updates
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/misc-updates
Khem Raj (7):
binutils_2.22: Backport to fix bogus textrels
rpm: Fix compilation on uclibc
pth: Mark incompatible with uclibc
libtool: Let -fstack-protector passed to link step
rpm: Use link time check for libssp
sat-solver: Fix build on uclibc
libzypp: Fix build with uclibc
.../binutils/binutils/0001-PR-ld-13470.patch | 82 ++++++++++++++++++++
meta/recipes-devtools/binutils/binutils_2.22.bb | 3 +-
meta/recipes-devtools/libtool/libtool-2.4.2.inc | 3 +-
.../libtool/libtool/respect-fstack-protector.patch | 53 +++++++++++++
.../rpm/rpm/fstack-protector-configure-check.patch | 13 +++
meta/recipes-devtools/rpm/rpm/rpmatch.patch | 42 ++++++++++
meta/recipes-devtools/rpm/rpm/uclibc-support.patch | 69 ++++++++++++++++
meta/recipes-devtools/rpm/rpm_5.4.0.bb | 5 +-
meta/recipes-extended/libzypp/libzypp/cstdio.patch | 49 ++++++++++++
meta/recipes-extended/libzypp/libzypp_git.bb | 10 ++-
.../sat-solver/sat-solver/futimes.patch | 32 ++++++++
meta/recipes-extended/sat-solver/sat-solver_git.bb | 7 +-
meta/recipes-support/pth/pth_2.0.7.bb | 12 +++-
13 files changed, 371 insertions(+), 9 deletions(-)
create mode 100644 meta/recipes-devtools/binutils/binutils/0001-PR-ld-13470.patch
create mode 100644 meta/recipes-devtools/libtool/libtool/respect-fstack-protector.patch
create mode 100644 meta/recipes-devtools/rpm/rpm/fstack-protector-configure-check.patch
create mode 100644 meta/recipes-devtools/rpm/rpm/rpmatch.patch
create mode 100644 meta/recipes-devtools/rpm/rpm/uclibc-support.patch
create mode 100644 meta/recipes-extended/libzypp/libzypp/cstdio.patch
create mode 100644 meta/recipes-extended/sat-solver/sat-solver/futimes.patch
--
1.7.5.4
next reply other threads:[~2012-06-04 22:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 22:21 Khem Raj [this message]
2012-06-04 22:21 ` [PATCH 1/7] binutils_2.22: Backport to fix bogus textrels Khem Raj
2012-06-04 22:21 ` [PATCH 2/7] rpm: Fix compilation on uclibc Khem Raj
2012-06-05 0:14 ` Flanagan, Elizabeth
2012-06-04 22:21 ` [PATCH 3/7] pth: Mark incompatible with uclibc Khem Raj
2012-06-04 22:21 ` [PATCH 4/7] libtool: Let -fstack-protector passed to link step Khem Raj
2012-06-04 22:21 ` [PATCH 5/7] rpm: Use link time check for libssp Khem Raj
2012-06-04 22:21 ` [PATCH 6/7] sat-solver: Fix build on uclibc Khem Raj
2012-06-04 22:21 ` [PATCH 7/7] libzypp: Fix build with uclibc Khem Raj
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.1338848379.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