From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12581] New: 2020.02-rc1 glibc failing to build on fedora 31
Date: Tue, 25 Feb 2020 10:38:51 +0000 [thread overview]
Message-ID: <bug-12581-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=12581
Bug ID: 12581
Summary: 2020.02-rc1 glibc failing to build on fedora 31
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: ian_ormshaw at waters.com
CC: buildroot at uclibc.org
Target Milestone: ---
I'm trying to build release 2020.02-rc1 on Fedora 31 and glibc is failinf to
build .
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-02-25 10:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 10:38 bugzilla at busybox.net [this message]
2020-02-25 10:42 ` [Buildroot] [Bug 12581] 2020.02-rc1 glibc failing to build on fedora 31 bugzilla at busybox.net
2020-02-25 10:44 ` bugzilla at busybox.net
2020-02-25 10:45 ` bugzilla at busybox.net
2020-02-26 8:09 ` bugzilla at busybox.net
2020-02-26 9:19 ` bugzilla at busybox.net
2020-02-26 15:15 ` 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-12581-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.