All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13806] New: Building host-localedef fails on fedora 34/gcc 11
Date: Fri, 14 May 2021 10:19:46 +0000	[thread overview]
Message-ID: <bug-13806-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=13806

            Bug ID: 13806
           Summary: Building host-localedef  fails on fedora 34/gcc 11
           Product: buildroot
           Version: 2021.02
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: ian_ormshaw at waters.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

Created attachment 8946
  --> https://bugs.busybox.net/attachment.cgi?id=8946&action=edit
error from build output

When building under fedora 34 x86_64 with gcc (GCC) 11.1.1 20210428 (Red Hat
11.1.1-1)
compilation fails with the attached error.  I haven't seen this before so I
assume it is a gcc 11 specific issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2021-05-14 10:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-14 10:19 bugzilla at busybox.net [this message]
2021-05-14 10:21 ` [Buildroot] [Bug 13806] Building host-localedef fails on fedora 34/gcc 11 bugzilla at busybox.net
2021-05-14 13:24 ` bugzilla at busybox.net
2021-05-14 17:59 ` bugzilla at busybox.net
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@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 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.