public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joao.moreira at intel dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/27080] New: Upstream glibc configure braeks with latest nm package in Fedora
Date: Wed, 16 Dec 2020 10:08:39 +0000 [thread overview]
Message-ID: <bug-27080-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27080
Bug ID: 27080
Summary: Upstream glibc configure braeks with latest nm package
in Fedora
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: build
Assignee: unassigned at sourceware dot org
Reporter: joao.moreira at intel dot com
CC: carlos at redhat dot com
Target Milestone: ---
Upstream glibc configure breaks when invoked with GNU nm version
2.35.50.0.1.20201215, which is the latest Fedora 33 version for nm. Invoking nm
over a manually compiled test will result in the following output, which seems
to be the cause of the error in configure:
bfd plugin: No register_all_symbols_read hook
Error message during configure is:
checking for __builtin_trap with no external dependencies... configure: error:
confusing output from nm -u
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-12-16 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 10:08 joao.moreira at intel dot com [this message]
2020-12-16 10:12 ` [Bug build/27080] " joao.moreira at intel dot com
2020-12-16 10:16 ` joao.moreira at intel dot com
2020-12-16 10:17 ` schwab@linux-m68k.org
2020-12-16 10:20 ` joao.moreira at intel dot com
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-27080-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).