From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13806] Building host-localedef fails on fedora 34/gcc 11
Date: Fri, 14 May 2021 17:59:13 +0000 [thread overview]
Message-ID: <bug-13806-163-F04F1AK3eQ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-13806-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=13806
--- Comment #2 from Peter Seiderer <ps.report@gmx.net> ---
Seems the problem is fixed upstream with the following two patches:
- Fix GCC 11 -Warray-parameter warning for __sigsetjmp (bug 26647) [1]
- Avoid -Wstringop-overflow warning in pthread_cleanup_push macros [2]
Can you test the following buildroot patch (backporting thr two commits for the
localedef package)?
https://patchwork.ozlabs.org/project/buildroot/patch/20210514175429.20552-1-ps.report at gmx.net/
[1]
https://github.com/bminor/glibc/commit/19302b27bdacfe87e861ff46fc0fbad60dd6602d
[2]
https://github.com/bminor/glibc/commit/548f467fa14ffe7d955beeb31b30e2aeae4467e0
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-14 17:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 10:19 [Buildroot] [Bug 13806] New: Building host-localedef fails on fedora 34/gcc 11 bugzilla at busybox.net
2021-05-14 10:21 ` [Buildroot] [Bug 13806] " bugzilla at busybox.net
2021-05-14 13:24 ` bugzilla at busybox.net
2021-05-14 17:59 ` bugzilla at busybox.net [this message]
2021-05-15 11:29 ` bugzilla at busybox.net
2021-05-17 6:10 ` bugzilla at busybox.net
2021-05-17 6:13 ` bugzilla at busybox.net
2021-05-17 8:50 ` bugzilla at busybox.net
2021-05-17 8:53 ` bugzilla at busybox.net
2021-05-17 18:29 ` bugzilla at busybox.net
2021-05-18 6:17 ` bugzilla at busybox.net
2021-05-18 21:31 ` bugzilla at busybox.net
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=bug-13806-163-F04F1AK3eQ@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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