From: john@ziaspace.com
To: Bruno Haible <bruno@clisp.org>
Cc: Thomas Klausner <wiz@netbsd.org>, js@netbsd.org, bug-gnulib@gnu.org
Subject: Re: pkgsrc m4 patches
Date: Tue, 29 Jun 2021 01:36:42 +0000 (UTC) [thread overview]
Message-ID: <Pine.NEB.4.64.2106290126570.13149@sparky.zia.io> (raw)
In-Reply-To: <2375309.9fctQjVWc2@omega>
>> I just updated m4 in pkgsrc to 1.4.19 and noticed that I could remove
>> almost all patches. Thank you for that!
>>
>> Then I thought I'd point out the remaining ones to you in the hope we
>> can get rid of those as well.
>>
>> The first one is ancient, in pkgsrc since at least 2013; it's for the
>> NetBSD vax port. I don't know more than that about it. jklos committed
>> it, so perhaps he has more details.
> Regarding NetBSD/vax support, I won't act because
> 1) the patch does not give background information,
> 2) I guess that this platform is in the same category as
> https://www.gnu.org/software/gnulib/manual/html_node/Unsupported-Platforms.html
> and all CPUs that were designed later than DEC alpha support
> IEEE 854 well, including NaNs.
VAX is certainly not in the same category as the examples on that page :P
That said, the patch isn't needed any more, since evaluation at compile
time doesn't happen any more.
Thanks,
John Klos
next prev parent reply other threads:[~2021-06-29 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210628183547.b4tcphi5urqsto3c@yt.nih.at>
2021-06-29 0:21 ` pkgsrc m4 patches Bruno Haible
2021-06-29 1:36 ` john [this message]
2021-06-29 5:26 ` Thomas Klausner
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.NEB.4.64.2106290126570.13149@sparky.zia.io \
--to=john@ziaspace.com \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=js@netbsd.org \
--cc=wiz@netbsd.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).