From: Nick Alcock <nick.alcock@oracle.com>
To: Nick Clifton <nickc@redhat.com>
Cc: binutils@sourceware.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 2/4 REVIEW] libtool.m4: fix nm BSD flag detection
Date: Wed, 07 Jul 2021 20:03:45 +0100 [thread overview]
Message-ID: <87pmvuc5f2.fsf@esperi.org.uk> (raw)
In-Reply-To: <82c38e53-9f97-8f7d-b1f7-9a9e45aacfa1@redhat.com> (Nick Clifton's message of "Wed, 7 Jul 2021 15:39:23 +0100")
On 7 Jul 2021, Nick Clifton told this:
> Hi Nick,
>
>> Ping?
>
> Oops.
I sent a bunch of pings out at the same time, to a bunch of different
projects. You are the only person to respond, so thank you!
>>> PR libctf/27482
>>> * libtool.m4 (LT_PATH_NM): Try BSDization flags with a user-provided
>
> Changes to libtool need to be posted to the libtool project:
>
> https://www.gnu.org/software/libtool/
I considered this, but there is *serious* divergence between the
libtool.m4 in our tree and upstream. Fixing this divergence looks to be
a fairly major project in and of itself :( the last real sync looked
like being all the way back in 2008.
> They have mailing lists for bug reports and patch submissions.
>
> Once the patch has been accepted there it can be backported to the gcc and
> gdb/binutils repositories...
AIUI, libtool has no maintainer currently, and the divergence is such
that the patch might need a near-complete rewrite anyway :( (there were
changes to this function upstream in 2012 and 2013, long after our last
sync.)
(However, I'm going to try in any case. I may have found a sucker, er, I
mean coworker willing to take this on.)
next prev parent reply other threads:[~2021-07-07 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 16:13 [PATCH 0/4 REVIEW] libtool and libctf fixes for Solaris 11 Nick Alcock
2021-06-25 16:13 ` [PATCH 1/4] libtool.m4: augment symcode " Nick Alcock
2021-06-25 16:13 ` [PATCH 2/4 REVIEW] libtool.m4: fix nm BSD flag detection Nick Alcock
2021-07-06 19:37 ` Nick Alcock
2021-07-07 14:39 ` Nick Clifton
2021-07-07 19:03 ` Nick Alcock [this message]
2021-07-21 8:22 ` Alan Modra
2021-09-09 12:39 ` Nick Alcock
2021-06-25 16:13 ` [PATCH 3/4] libctf: try several possibilities for linker versioning flags Nick Alcock
2021-06-25 16:13 ` [PATCH 4/4] configure: regenerate in all projects that use libtool.m4 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=87pmvuc5f2.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=nickc@redhat.com \
/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).