From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] uclibc: update to 1.0.20
Date: Sun, 4 Dec 2016 15:36:21 +0100 [thread overview]
Message-ID: <20161204153621.5d66d8a6@free-electrons.com> (raw)
In-Reply-To: <20161204112026.GA30258@waldemar-brodkorb.de>
Hello,
On Sun, 4 Dec 2016 12:20:27 +0100, Waldemar Brodkorb wrote:
> The test suite is removed from the package and is already a separate
> package in buildroot. All patches are upstream, so remove them.
> The UCLIBC_HAS_LFS option is removed upstream.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> .../0001-linuxthreads-add-back-signal.h.patch | 28 ---------
> ...ne-madvise-related-macros-for-noMMU-targe.patch | 66 ----------------------
> ...003-posix_madvise-not-available-for-noMMU.patch | 30 ----------
> package/uclibc/uclibc.hash | 2 +-
> package/uclibc/uclibc.mk | 30 +---------
> 5 files changed, 2 insertions(+), 154 deletions(-)
> delete mode 100644 package/uclibc/0001-linuxthreads-add-back-signal.h.patch
> delete mode 100644 package/uclibc/0002-do-not-define-madvise-related-macros-for-noMMU-targe.patch
> delete mode 100644 package/uclibc/0003-posix_madvise-not-available-for-noMMU.patch
You forgot to remove the BR2_UCLIBC_INSTALL_TEST_SUITE from the
Config.in. So I've done that, and added the necessary logic in
Config.in.legacy.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-12-04 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 11:20 [Buildroot] [PATCH] uclibc: update to 1.0.20 Waldemar Brodkorb
2016-12-04 14:36 ` Thomas Petazzoni [this message]
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=20161204153621.5d66d8a6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox