Thanks for writing all that. One comment about the list containing this item:
+@item
+If your program opens only one new file descriptor or FILE stream at a time,
+it is @emph{not affected}.
Isn't the problem more general than what this list suggests? Considering the
list item quoted above, eve
Thanks for the xstdopen module; it simplifies diffutils and I installed the
attached patches there for it.
>From 86ece0ee216910bce0dbceb60b98190bf8f93702 Mon Sep 17 00:00:00 2001
From: Paul Eggert
Date: Sun, 6 Jan 2019 17:15:06 -0800
Subject: [PATCH 1/2] build: update gnulib submodule to latest
Bruno Haible wrote:
That build failure occurred even with the Gnulib module 'c99' included.
When this topic came up in 2017, you asked whether we should bury support for
IRIX cc[1], I opined that we should drop support[2], and Tom G. Christensen said
you needed MIPSpro 7.4.0 or later for c99
I wrote:
> I would like to use this modules in GNU gettext and GNU libiconv.
Well, I thought that most programs do need one form of the mitigation
against the closed file descriptors. I'm surprised to see not the case
for any of the programs from GNU gettext and GNU libiconv.
This deserves some d
PS:
> 1) A compilation failure with IRIX cc:
That build failure occurred even with the Gnulib module 'c99' included.
Bruno
Paul Eggert wrote:
> I resurrected and refreshed that old Coreutils code and put it into a new
> Gnulib
> module stdopen
I would like to use this modules in GNU gettext and GNU libiconv. But I'm
encountering two issues:
1) A compilation failure with IRIX cc:
cc -n32 -DHAVE_CONFIG_H -I. -I../..
Bruno Haible wrote:
The feature is not portable to POSIX
platforms. Besides, I doubt whether anybody is using the feature anyway.
OK, if you question the "feature" as a whole,
Sorry, I was referring only to the never-used feature of diffutils, where "-" in
a command-line argument stands for
[CCing bug-gnulib. This is a followup to
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33965 ]
Hi Paul,
> The feature is not portable to POSIX
> platforms. Besides, I doubt whether anybody is using the feature anyway.
OK, if you question the "feature" as a whole, then I'd say:
* Users don't
