Autoconf 2.60 won't declare 'exit' for you automatically, due to severe
portability hassles in trying to do this. I installed the following
changes to gnulib to accommodate this. These changes also fix some
related portability problems that I discovered in the neighborhood,
e.g., other undeclared
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 4/24/2006 1:38 AM:
> Autoconf 2.60 won't declare 'exit' for you automatically, due to severe
> portability hassles in trying to do this. I installed the following
> changes to gnulib to accommodate this. These changes also
Karl Berry wrote:
> First, regarding gnulib-tool --help.
>
> --update isn't mentioned under "Operation modes:", although it is one
> of the usages.
I'm adding this doc:
--update update the current package, restore files omitted
from CVS
> I suggest
Karl Berry wrote on 2006-02-13:
> Bruce Korb implemented a library for straightforward config file
> parsing (among other things). We thought it would make sense to use it
> for GNU Hello, as an example of how it can be done.
How come so few programs use this libopts? Let me look at the syntax of
Paul Eggert wrote on 2006-02-17:
> > Either we need to update the various gnulib macros
> > borrowed from CVS autoconf to override bugs in autoconf 2.59, or we need
> > to release autoconf 2.60.
>
> We should do both, since we can't assume 2.60 will be adopted right
> away. What changes need to
Sergey Poznyakoff wrote on 2006-02-25:
> They should all go through TP, certainly. Apart from the reasons, listed
> by Jim, there are two more:
>
> - TP checks that the translator fills assignment papers, which is
> especially important for GNU programs.
> - Other translators from the submitter'
Paul Eggert wrote on 2006-02-26:
> While we're on the subject, is the translation project on hiatus right
> now? They haven't updated the Bison .pot file even though I sent them
> email thirteen days ago about the Bison 2.1a version (a version
> generated principally in order to get translations),
Ben Pfaff wrote on 2006-02-27:
> I'm not sure I understand the fwriteerror() interface.
The basic idea is to be able to write:
output_file = fopen (file_name, "w");
if (output_file == NULL)
error (EXIT_FAILURE, errno, _("error while opening \"%s\" for writing"),
file_na
Ralf Wildenhues wrote on 2006-03-03:
> On powerpc-ibm-aix5.3.0.0, poll is not deemed acceptable: the test in
> m4/poll.m4 fails because polling on /dev/null does not work. It does
> work to poll on regular files, though. Polling on /dev/tty does not
> work either.
Thanks for the report. I'm chan
Ralf Wildenhues wrote on 2006-03-03:
> the test is fine, but the build fails later:
>
> | xlc -DHAVE_CONFIG_H -DEXEEXT=\"\" -DEXEEXT=\"\"
> -DLIBDIR=\"/usr/local/lib\" -I. -I../../dummy-0/lib -I..-D_THREAD_SAFE
> -g -c ../../dummy-0/lib/poll.c
> | "../../dummy-0/lib/poll.c", line 5
Claudio Fontana wrote on 2006-03-04:
> while trying to improve current support in gnulib for internal gettext,
> I produced this patch, which I use successfully in the packages I
> maintain to support per-package additions to AM_CPPFLAGS.
>
> The patch is a unified p1 diff.
> I suggest this for in
Paul Eggert wrote on 2006-03-08:
> I installed these I-hope-obvious improvements to the unistd module.
> I didn't touch the modules Bruno maintains, which might also benefit
> from the unistd module.
Thanks. This 'unistd' module is the best invention since .
I'm applying the same change to all mod
Paul Eggert wrote on 2006-03-10:
> I recently redisovered the fact that asctime_r and ctime_r, like
> asctime and ctime, are unsafe functions in the same sense that gets is
> unsafe: they can overrun their output buffers and there's no simple
> way for the user to detect in advance whether this wil
Antonio Diaz Diaz wrote on 2006-03-16:
> By the way. Just now I have found the file patch-2.5.9.tar.gz (date
> 1-Jun-2004) in the directory ftp://alpha.gnu.org/gnu/diffutils/ after
> spending more than ten hours patching and cleaning patch-2.5.4 (the
> latest stable release). :-(
When looking f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 4/24/2006 6:12 AM:
> Paul Eggert wrote on 2006-03-10:
>> I recently redisovered the fact that asctime_r and ctime_r, like
>> asctime and ctime, are unsafe functions in the same sense that gets is
>> unsafe: they can overrun
On 4/24/06, Bruno Haible <[EMAIL PROTECTED]> wrote:
Karl Berry wrote on 2006-02-13:> Bruce Korb implemented a library for straightforward config file
> parsing (among other things). We thought it would make sense to use it> for GNU Hello, as an example of how it can be done.How come so few program
In the latest patch, those three gotos confused me. Part of the
confusion is due to uses like 'if (fflush (fp))' which are of course
valid but which I find a bit hard to read at first. Also, the
comment's "contents is" is not quite grammatical, and the comment is a
bit overconfident about getting
Paul Eggert <[EMAIL PROTECTED]> writes:
> In the latest patch, those three gotos confused me. Part of the
> confusion is due to uses like 'if (fflush (fp))' which are of course
> valid but which I find a bit hard to read at first. Also, the
> comment's "contents is" is not quite grammatical, and
Eric Blake <[EMAIL PROTECTED]> writes:
> Doesn't gnulib assume C89 or better; and shouldn't tests be made to
> work with C++ as a C compiler when possible?
Thanks, I installed this as well (in coreutils and gnulib).
2006-04-24 Paul Eggert <[EMAIL PROTECTED]>
* m4/unlink-busy.m4 (gl_FU
Bruno Haible <[EMAIL PROTECTED]> writes:
> Unlike gets() and the termcap functions, these functions don't need a buffer
> of arbitrary size. Only the initially specified size was too small. The
> functions would be OK to use in GNU programs if a buffer of size 100 was
> used rather than a buffer o
Hi,
This module 'iconvstring' is in use in GNU gettext in 4 places. It is an
easy-to-use iconv() wrapper, like the 'iconvme' module. The difference is
that 'iconvstring' uses an iconv_t descriptor, rather than two encoding names,
and is therefore suitable for converting a whole lot of strings, wit
gnulib-tool appears to blindly sort the list of #include
directives it prints. When the list contains #if...#endif, that
makes the output funny, e.g.:
You may need to add #include directives for the following .h files.
#endif
#if HAVE_MBRTOWC
#if HAVE_WCHAR_H && HAVE_WCTYPE_
22 matches
Mail list logo
