From: anton baltser <anton@blok-box.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, elfutils-devel@sourceware.org
Subject: Re: Fwd: Anton Baltser, bug with libdebuginfod
Date: Mon, 31 Jul 2023 18:47:09 +0300 [thread overview]
Message-ID: <CAMsp4fDJ_VRGX1sN2QYXOh8-KgQVy6L_TTVxcL45VnJWDE8Chw@mail.gmail.com> (raw)
In-Reply-To: <6c519884623385c5824609ff00966f7c5a9b9590.camel@klomp.org>
[-- Attachment #1: Type: text/plain, Size: 1432 bytes --]
Yes, it works! Thanks for your help!
On Mon, Jul 31, 2023, 18:43 Mark Wielaard <mark@klomp.org> wrote:
> Hi Anton,
>
> On Sun, 2023-07-30 at 22:05 +0300, anton baltser wrote:
> > Thanks for the quick response.
> > I did:
> > $ ./configure --prefix=/usr \
> > > --disable-debuginfod \
> > > --enable-libdebuginfod=dummy \
> > > --libdir=/libm
> > $ make install :
> > Making install in tests
> > make[2]: Nothing to be done for 'install-exec-am'.
> > make[2]: Nothing to be done for 'install-data-am'.
> > make[2]: Nothing to be done for 'install-exec-am'.
> > /usr/bin/mkdir -p '/usr/include/elfutils'
> > /usr/bin/install -c -m 644 version.h '/usr/include/elfutils'
> [...]
>
> So this will also install debuginfod.h under /usr/include/elfutils
> Is that what you are asking about? Is it not doing that for you?
>
> > $ make check :
> >
> ============================================================================
> > Testsuite summary for elfutils 0.189
> >
> ============================================================================
> > # TOTAL: 236
> > # PASS: 232
> > # SKIP: 4
> > # XFAIL: 0
> > # FAIL: 0
> > # XPASS: 0
> > # ERROR: 0
> >
> ============================================================================
> > make[1]: Nothing to be done for 'check-am'.
> >
> > Is that right result?
>
> That looks correct yes.
>
> Cheers,
>
> Mark
>
prev parent reply other threads:[~2023-07-31 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMsp4fAUYQKTQYCUU2v4838Uy=zeEaxCV4ZEu3AHMeuMZ8RF2Q@mail.gmail.com>
2023-07-30 17:15 ` anton baltser
2023-07-30 18:26 ` Frank Ch. Eigler
2023-07-30 19:05 ` anton baltser
2023-07-31 15:43 ` Mark Wielaard
2023-07-31 15:47 ` anton baltser [this message]
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=CAMsp4fDJ_VRGX1sN2QYXOh8-KgQVy6L_TTVxcL45VnJWDE8Chw@mail.gmail.com \
--to=anton@blok-box.com \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.com \
--cc=mark@klomp.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).