From: Thomas Klausner <wiz@netbsd.org>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, js@netbsd.org, jklos@netbsd.org
Subject: Re: pkgsrc m4 patches
Date: Tue, 29 Jun 2021 07:26:43 +0200 [thread overview]
Message-ID: <20210629052643.5vdk7p2pfkm3rsvi@yt.nih.at> (raw)
In-Reply-To: <2375309.9fctQjVWc2@omega>
On Tue, Jun 29, 2021 at 02:21:47AM +0200, Bruno Haible wrote:
> [CCing bug-gnulib. We work in public; please avoid private email if
> there is a mailing list.]
Sorry, I'll keep that in mind.
> Thomas Klausner wrote:
> > Hi Bruno!
> >
> > 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.
> >
> > The other one is more recent and was committed as a "fix for QNX". js
> > committed it and might know more.
>
> > [2 patches from http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/devel/m4/patches/]
>
> Thanks Thomas for the pointer.
>
> 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.
After jklos' message, I've removed this patch from pkgsrc.
> Regarding the strerror-override module: There is indeed the possibility
> that strerror-override.c gets compiled even though strerror_override is
> defined as a macro.
>
> Fixing it like this. A separate macro is used so that config.h files can do
> #define strerror_override libfoo_strerror_override
> (when cleaning up the namespace of symbols exported by a library libfoo).
Thanks!
Thomas
prev parent reply other threads:[~2021-06-29 5:27 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
2021-06-29 5:26 ` Thomas Klausner [this message]
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=20210629052643.5vdk7p2pfkm3rsvi@yt.nih.at \
--to=wiz@netbsd.org \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=jklos@netbsd.org \
--cc=js@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).