From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Fix coreutils build on uclibc
Date: Thu, 4 Apr 2013 17:38:40 -0700 [thread overview]
Message-ID: <cover.1365122145.git.raj.khem@gmail.com> (raw)
coreutils after upgrade has started to fail to build on uclibc
targets, this series of patches fix the build on uclibc as well
as on eglibc is working normal.
The following changes since commit 2587a33134fde80dd1367629d9def45ac70256ee:
site: add endianness information for libmemcached (2013-04-04 23:58:00 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib kraj/coreutils
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/coreutils
Khem Raj (1):
coreutils: Fix build on uclibc after upgrade to 8.21
...d-ltr-and-lpthread-for-getting-spawn-func.patch | 15 ++++
...sys_time.in.h-Fix-use-of-restrict-keyword.patch | 51 +++++++++++++
.../coreutils/coreutils-8.21/gcc-uclibc.patch | 77 ++++++++++++++++++++
meta/recipes-core/coreutils/coreutils_8.21.bb | 5 +-
4 files changed, 147 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-core/coreutils/coreutils-8.21/0001-local.mk-Add-ltr-and-lpthread-for-getting-spawn-func.patch
create mode 100644 meta/recipes-core/coreutils/coreutils-8.21/0001-sys_time.in.h-Fix-use-of-restrict-keyword.patch
create mode 100644 meta/recipes-core/coreutils/coreutils-8.21/gcc-uclibc.patch
--
1.7.9.5
next reply other threads:[~2013-04-05 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 0:38 Khem Raj [this message]
2013-04-05 0:39 ` [PATCH 1/1] coreutils: Fix build on uclibc after upgrade to 8.21 Khem Raj
2013-04-05 13:55 ` [PATCH 0/1] Fix coreutils build on 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.1365122145.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 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.