From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/3] uclibc: build fixes for xtensa snapshot version
Date: Mon, 13 Jan 2014 08:26:11 +0200 [thread overview]
Message-ID: <cover.1389594195.git.baruch@tkos.co.il> (raw)
This series bumps xtensa default uclibc version to add upstream fixes to
autobuild failures. This series also adds a uclibc patch to fix posix_spawn
autoconf detection.
The last patch in this series reverts a previous e2fsprogs fix that is both
wrong and is superseded by the xtensa posix_fadvise fix in upstream uclibc.
v2:
* Bump uclibc version
* Remove patches applied upstream
Baruch Siach (3):
uclibc: bump xtensa snapshot version
uclibc: xtensa: fix posix_spawn autoconf detection
Revert "e2fsprogs: fix posix_fadvise() signature mismatch"
...g-fix-build-when-posix_fadvise-is-missing.patch | 42 ------
.../0001-spawn-move-from-librt-to-libc.patch | 142 +++++++++++++++++++++
package/uclibc/Config.in | 2 +-
3 files changed, 143 insertions(+), 43 deletions(-)
delete mode 100644 package/e2fsprogs/e2fsprogs-0002-e4defrag-fix-build-when-posix_fadvise-is-missing.patch
create mode 100644 package/uclibc/7bf35c8b7d4a1f97174eb49f47f33946b282114c/0001-spawn-move-from-librt-to-libc.patch
--
1.8.5.2
next reply other threads:[~2014-01-13 6:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 6:26 Baruch Siach [this message]
2014-01-13 6:26 ` [Buildroot] [PATCH v2 1/3] uclibc: bump xtensa snapshot version Baruch Siach
2014-01-20 21:37 ` Peter Korsgaard
2014-01-13 6:26 ` [Buildroot] [PATCH v2 2/3] uclibc: xtensa: fix posix_spawn autoconf detection Baruch Siach
2014-01-15 13:31 ` Baruch Siach
2014-01-15 14:30 ` Peter Korsgaard
2014-01-13 6:26 ` [Buildroot] [PATCH v2 3/3] Revert "e2fsprogs: fix posix_fadvise() signature mismatch" Baruch Siach
2014-01-20 21:37 ` Peter Korsgaard
2014-01-13 8:13 ` [Buildroot] [PATCH v2 0/3] uclibc: build fixes for xtensa snapshot version Thomas Petazzoni
2014-01-13 8:23 ` Baruch Siach
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.1389594195.git.baruch@tkos.co.il \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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.