From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [dora][RFC PATCH 0/2] dpkg changes to support CentOS 5.8 hosts
Date: Thu, 21 Nov 2013 01:08:20 -0600 [thread overview]
Message-ID: <1385017702-22903-1-git-send-email-mark.hatle@windriver.com> (raw)
Since CentOS 5.8 isn't considered supported by oe-core, this is just an RFC.
It's being sent for Yocto Project compliance reasons.
Lei Liu (2):
dpkg: Fix a build error for dpkg-native on CentOS 5.8.
dpkg: Fix a link problem for dpkg-native on CentOS 5.8.
.../dpkg/dpkg/glibc2.5-sync_file_range.patch | 86 ++++++++++++++++++++++
.../dpkg/dpkg/no-vla-warning.patch | 24 ++++++
meta/recipes-devtools/dpkg/dpkg_1.17.1.bb | 2 +
3 files changed, 112 insertions(+)
create mode 100644 meta/recipes-devtools/dpkg/dpkg/glibc2.5-sync_file_range.patch
create mode 100644 meta/recipes-devtools/dpkg/dpkg/no-vla-warning.patch
--
1.8.1.2.545.g2f19ada
next reply other threads:[~2013-11-21 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 7:08 Mark Hatle [this message]
2013-11-21 7:08 ` [dora][RFC PATCH 1/2] dpkg: Fix a build error for dpkg-native on CentOS 5.8 Mark Hatle
2013-11-21 7:08 ` [dora][RFC PATCH 2/2] dpkg: Fix a link problem " Mark Hatle
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=1385017702-22903-1-git-send-email-mark.hatle@windriver.com \
--to=mark.hatle@windriver.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