From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/uclibc-ng-test: disable tst-cond22 with glibc based toolchain
Date: Sat, 13 May 2017 14:58:24 +0200 [thread overview]
Message-ID: <20170513145824.7373c3c9@free-electrons.com> (raw)
In-Reply-To: <20170513123636.23978-1-romain.naour@gmail.com>
Hello,
On Sat, 13 May 2017 14:36:36 +0200, Romain Naour wrote:
> uclibc-ng-test is broken with glibc 2.25 due to pthread_cond_t changes
> introduced by [1].
> Waldemar has disabled this test (tst-cond22) with glibc based toolchain
> [2] but the current uclibc-ng-test package doesn't contain this patch.
>
> So here it is.
>
> Fixes:
> [nios2] http://autobuild.buildroot.net/results/d61c8d169fc070271114a515159650f7a0f333c0
> [arm] http://autobuild.buildroot.net/results/22295711046c519df44d5d976e0bfcae1f006e5a
>
> [1] https://sourceware.org/git/?p=glibc.git;a=commit;h=ed19993b5b0d05d62cc883571519a67dae481a14
> [2] https://gogs.waldemar-brodkorb.de/linux/uclibc-ng-test/commit/787e584f18afc967d91cfe1a8443df2657579ecb
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: Waldemar Brodkorb <wbx@openadk.org>
> ---
> .../uclibc-ng-test/0001-disable-for-glibc.patch | 40 ++++++++++++++++++++++
> 1 file changed, 40 insertions(+)
> create mode 100644 package/uclibc-ng-test/0001-disable-for-glibc.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-13 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 12:36 [Buildroot] [PATCH] package/uclibc-ng-test: disable tst-cond22 with glibc based toolchain Romain Naour
2017-05-13 12:58 ` 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=20170513145824.7373c3c9@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