From: "mliska at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/29714] New: debuginfod rely on gcc being configured with --enable-linker-build-i
Date: Fri, 21 Oct 2022 15:16:15 +0000 [thread overview]
Message-ID: <bug-29714-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29714
Bug ID: 29714
Summary: debuginfod rely on gcc being configured with
--enable-linker-build-i
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: mliska at suse dot cz
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
FAIL: run-debuginfod-federation-sqlite.sh
...
++ ... /home/marxin/Programming/elfutils/tests/../src/readelf -a L/foo
++ grep 'Build ID'
++ cut -d ' ' -f 7
+ BUILDID=
where L/foo is symlink to
+ ln -s /home/marxin/Programming/elfutils/tests/dwfllines L/foo
and this file is not explicitly linked with -Wl,--build-id:
rm dwfllines ; make V=1 dwfllines
gcc -std=gnu99 -Wall -Wshadow -Wformat=2 -Wold-style-definition
-Wstrict-prototypes -Wtrampolines -Wlogical-op -Wduplicated-cond
-Wnull-dereference -Wimplicit-fallthrough=5 -Werror -Wunused -Wextra
-Wstack-usage=262144 -D_FORTIFY_SOURCE=3 -g -O2
-Wl,-rpath-link,../libasm:../libdw:../libelf -o dwfllines dwfllines.o
../lib/libeu.a ../libdw/libdw.so ../libelf/libelf.so
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-10-21 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 15:16 mliska at suse dot cz [this message]
2022-10-21 15:45 ` [Bug debuginfod/29714] " mark at klomp dot org
2022-10-21 17:18 ` mliska at suse dot cz
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-29714-10460@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).