From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libdw/24856] dwarf_diename() cannot get correct name
Date: Sat, 27 Jul 2019 14:29:00 -0000 [thread overview]
Message-ID: <bug-24856-10460-Kbh4C9jk7b@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-24856-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24856
--- Comment #3 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Changbin Du from comment #1)
> BTW, the latest master branch has build failure.
>
> CCLD libebl_sparc.so
> CCLD libebl_ppc.so
> CCLD libebl_ppc64.so
> CCLD libebl_s390.so
> CCLD libebl_tilegx.so
> CCLD libebl_m68k.so
> CCLD libebl_bpf.so
> AR libebl_riscv_pic.a
> CCLD libebl_riscv.so
> /usr/bin/ld: libebl_riscv_pic.a(riscv_init.os): relocation R_X86_64_PC32
> against undefined hidden symbol `riscv64_core_note' can not be used when
> making a shared object
> /usr/bin/ld: final link failed: nonrepresentable section on output
> collect2: error: ld returned 1 exit status
> make[2]: *** [Makefile:1299: libebl_riscv.so] Error 1
> make[1]: *** [Makefile:486: all-recursive] Error 1
> make: *** [Makefile:402: all] Error 2
That is surprising, obviously that doesn't happen on any of the buildbots. You
might want to open a different bug for this issue (because it seems totally
unrelated to this issue) explaining how you configured, which gcc and ld
versions you are using and maybe the output of make V=1 to show the command
line flags (also make sure you make distclean first).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-07-27 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-27 13:40 [Bug libdw/24856] New: " changbin.du at gmail dot com
2019-07-27 13:46 ` [Bug libdw/24856] " changbin.du at gmail dot com
2019-07-27 14:28 ` mark at klomp dot org
2019-07-27 14:29 ` mark at klomp dot org [this message]
2020-01-10 15:14 ` fche at redhat 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-24856-10460-Kbh4C9jk7b@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).