From: "schwab@linux-m68k.org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/30812] New: ../libelf/gelf.h:32:10: fatal error: libelf.h: No such file or directory
Date: Wed, 30 Aug 2023 15:26:05 +0000 [thread overview]
Message-ID: <bug-30812-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30812
Bug ID: 30812
Summary: ../libelf/gelf.h:32:10: fatal error: libelf.h: No such
file or directory
Product: elfutils
Version: unspecified
Status: NEW
Keywords: testsuite
Severity: normal
Priority: P2
Component: general
Assignee: unassigned at sourceware dot org
Reporter: schwab@linux-m68k.org
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
Building the test system-elf-gelf-test fails with:
gcc -D_GNU_SOURCE -DHAVE_CONFIG_H -DLOCALEDIR='"/usr/share/locale"' -I. -I..
-std=gnu99 -Wall -Wshadow -Wformat=2 -Wold-style-definition -Wstrict-prototypes
-Wtrampolines -Wlogical-op -Wduplicated-cond -Wnull-dereference
-Wimplicit-fallt
hrough=5 -Wuse-after-free=3 -Werror -Wunused -Wextra -Wstack-usage=262144 -O2
-Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=3 -fstack-protector-strong
-funwind-ta
bles -fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type
-
flto=auto -ffat-lto-objects -Werror=date-time -g -c -o
system_elf_gelf_test-syst
em-elf-gelf-test.o `test -f 'system-elf-gelf-test.c' || echo
'./'`system-elf-gelf-test.c
In file included from system-elf-gelf-test.c:22:
../libelf/gelf.h:32:10: fatal error: libelf.h: No such file or directory
32 | #include <libelf.h>
| ^~~~~~~~~~
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-08-30 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 15:26 schwab@linux-m68k.org [this message]
2023-08-30 15:47 ` [Bug general/30812] " mark at klomp dot org
2023-09-03 16:24 ` mark at klomp dot org
2023-09-04 11:41 ` mark at klomp dot org
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-30812-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).