public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug general/30812] ../libelf/gelf.h:32:10: fatal error: libelf.h: No such file or directory
Date: Wed, 30 Aug 2023 15:47:10 +0000	[thread overview]
Message-ID: <bug-30812-10460-xg9UKBBulL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30812-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30812

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at klomp dot org

--- Comment #1 from Mark Wielaard <mark at klomp dot org> ---
That is interesting. How are you building it?

The test should use the gelf.h and libelf.h from the current source tree, but
the system install libelf.

O... I see the testcase includes them as ../libelf/libelf.h and
../libelf/gelf.h, but then gelf.h itself does an #include <libelf.h> which
comes from the system path.

hmmm, so this is a build without libelf already installed.
Which of course is a valid setup. But have to think how to reorder the testcase
to work that way...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2023-08-30 15:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 15:26 [Bug general/30812] New: " schwab@linux-m68k.org
2023-08-30 15:47 ` mark at klomp dot org [this message]
2023-09-03 16:24 ` [Bug general/30812] " 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-xg9UKBBulL@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).