From: Nick Clifton <nickc@redhat.com>
To: Aaron Merey <amerey@redhat.com>,
gdb-patches@sourceware.org, binutils@sourceware.org
Cc: aburgess@redhat.com
Subject: Re: [PATCH 1/7] config/debuginfod.m4: Add check for libdebuginfod 0.188
Date: Wed, 27 Sep 2023 11:28:49 +0100 [thread overview]
Message-ID: <91cefe90-8960-3b0c-3ec2-7dd25768dd25@redhat.com> (raw)
In-Reply-To: <CAJDtP-SVHJbvgkQs4M0PY8hYkVdom+ywiCQCFz1YE5gVfFugRQ@mail.gmail.com>
Hi Aaron,
> Ping
Pong. Sorry for the delay in responding. I will blame
the GNU Tools Cauldron for the delay this time, although
really it is just me being occupied with too many other
things.
>> Add check for libdebuginfod 0.188 in AC_DEBUGINFOD and if found
>> define macro HAVE_LIBDEBUGINFOD_FIND_SECTION.
>>
>> This macro indicates support for downloading ELF sections from
>> debuginfod servers.
Patch approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2023-09-27 10:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230816044259.2675531-1-amerey@redhat.com>
2023-08-16 4:42 ` Aaron Merey
2023-09-19 14:33 ` Aaron Merey
2023-09-27 10:28 ` Nick Clifton [this message]
2023-09-27 19:14 ` Aaron Merey
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=91cefe90-8960-3b0c-3ec2-7dd25768dd25@redhat.com \
--to=nickc@redhat.com \
--cc=aburgess@redhat.com \
--cc=amerey@redhat.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@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).