From: Nick Alcock <nick.alcock@oracle.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 2/4] libtool.m4: adjust kludge for ignoring syntax errors
Date: Fri, 16 Dec 2022 15:11:09 +0000 [thread overview]
Message-ID: <87edszcrjm.fsf@esperi.org.uk> (raw)
In-Reply-To: <87y1r7ihct.fsf@igel.home> (Andreas Schwab's message of "Fri, 16 Dec 2022 14:54:42 +0100")
On 16 Dec 2022, Andreas Schwab stated:
> This should be reported upstream, and the solution imported from there.
Yes, but... upstream is semi-dead and very divergent from what we've got
(we're talking 13 years of accumulated differences by this point), so
doing that is a huge job, and far more likely to cause more breakage
than it fixes. I'm planning to push this fix at upstream too, but
they've not looked at the previous patches this is fixing yet either,
so...
--
NULL && (void)
next prev parent reply other threads:[~2022-12-16 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 13:25 [PATCH 0/4] A few backlogged build-system problems Nick Alcock
2022-12-16 13:25 ` [PATCH 1/4] ctf: fix various dreadful typos in the ctf_archive format comments Nick Alcock
2022-12-16 13:25 ` [PATCH 2/4] libtool.m4: adjust kludge for ignoring syntax errors Nick Alcock
2022-12-16 13:54 ` Andreas Schwab
2022-12-16 15:11 ` Nick Alcock [this message]
2022-12-16 15:18 ` Andreas Schwab
2022-12-19 17:30 ` Nick Alcock
2022-12-16 13:25 ` [PATCH 3/4] Regenerate affected configures Nick Alcock
2022-12-16 13:25 ` [PATCH 4/4] libctf: skip the testsuite from inside dejagnu Nick Alcock
2022-12-20 12:53 ` [PATCH 0/4] A few backlogged build-system problems Alan Modra
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=87edszcrjm.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=binutils@sourceware.org \
--cc=schwab@linux-m68k.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).