From: Nick Alcock <nick.alcock@oracle.com>
To: Indu Bhagat <indu.bhagat@oracle.com>
Cc: binutils@sourceware.org, vapier@gentoo.org
Subject: Re: [PATCH] libctf: use libtool for link test in configure
Date: Wed, 09 Nov 2022 10:54:22 +0000 [thread overview]
Message-ID: <87wn84xush.fsf@esperi.org.uk> (raw)
In-Reply-To: <20221108192248.1622627-1-indu.bhagat@oracle.com> (Indu Bhagat's message of "Tue, 8 Nov 2022 11:22:48 -0800")
On 8 Nov 2022, Indu Bhagat uttered the following:
> Looks like its better to deal with this patch out of the SFrame series. It has
> been discussed previously in the thread
> https://sourceware.org/pipermail/binutils/2022-November/124102.html
> and seems to be converging.
>
> Testing notes:
> - regression testing of libctf/ on x86_64-linux-gnu works well.
>
> OK for trunk?
My first impressions are that this looks good, but I'll throw it past my
usual test matrix before giving it a final ack: if that passes, it's OK.
(That this gives me the opportunity to test some outstanding binutils
things of mine at the same time, and that both changes involve libtool
so require similar sets of tests, is *pure coincidence*.)
--
NULL && (void)
next prev parent reply other threads:[~2022-11-09 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 19:22 Indu Bhagat
2022-11-09 10:54 ` Nick Alcock [this message]
2022-11-11 13:12 ` Nick Alcock
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=87wn84xush.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=binutils@sourceware.org \
--cc=indu.bhagat@oracle.com \
--cc=vapier@gentoo.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).