On 01-Nov-16 15:52, Eric Blake wrote:
Which version of GNU m4? There are some particular m4 bugs in some
older versions that kill configure scripts, so the bootstrap script
intentionally blacklists m4 versions with those bugs.
missed this. 1.4.17
Paul Eggert wrote:
> > Should this change be accompanied with a documentation change
> > in doc/posix-functions/utimensat.texi ?
>
> It's not strictly needed, as Gnulib still works around bugs in older
> systems, it's just that 'configure' now defaults to assuming the older
> bugs don't exist in
On 11/01/2016 11:20 AM, Bruno Haible wrote:
Should this change be accompanied with a documentation change
in doc/posix-functions/utimensat.texi ?
It's not strictly needed, as Gnulib still works around bugs in older
systems, it's just that 'configure' now defaults to assuming the older
bugs do
On 10/14/2016 11:47 PM, Jim Meyering wrote:
> I tried to build the coreutils using very recent GCC 7, built from
> latest git, and encountered a few new warnings (errors when configured
> with --enable-gcc-warnings), so wrote the following to address them.
> With these, everything now compiles warn
Hi Paul,
> We no longer need to worry
> about Linux kernel 2.6.32 when building with newer kernels.
Should this change be accompanied with a documentation change
in doc/posix-functions/utimensat.texi ?
And what about m4/futimens.m4 and doc/posix-functions/futimens.texi ?
Bruno
* lib/utimensat.c (rpl_utimensat): Update FIXME comment.
* m4/utimensat.m4 (gl_FUNC_UTIMENSAT): Belatedy do a "simplify
this in 2012" FIXME, by assuming the file system bug is absent
unless demonstrated to be present. We no longer need to worry
about Linux kernel 2.6.32 when building with newer ke
[re-adding gnulib; please remember to reply all]
On 11/01/2016 09:16 AM, Michael Felt wrote:
>> [adding gnulib]
>>
>> Can you figure out which sed script in the bootstrap script is
>> triggering this extra output, and/or provide the edits that work for
>> you, as you hinted above?
> In get_versio
[adding gnulib]
On 11/01/2016 08:47 AM, mich...@felt.demon.nl wrote:
> ok - how do I submit a patch.
'git send-email' is preferred, but any way of creating the patch and
mailing it to the list can probably work as a starting point.
>
> An issue I have is the syntax for sed in ./bootstrap.
If b
