GNU bug report logs - #5999
new snapshot available: coreutils-8.4.100-81926

Previous Next

Package: coreutils;

Reported by: Jim Meyering <jim <at> meyering.net>

Date: Wed, 21 Apr 2010 20:34:02 UTC

Severity: normal

Done: Jim Meyering <jim <at> meyering.net>

Bug is archived. No further changes may be made.

Full log


Message #26 received at 5999-done <at> debbugs.gnu.org (full text, mbox):

From: Jim Meyering <jim <at> meyering.net>
To: "Gilles Espinasse" <g.esp <at> free.fr>
Cc: bug-gnulib <at> gnu.org, Paolo Bonzini <bonzini <at> gnu.org>,
	Bruno Haible <bruno <at> clisp.org>, 5999-done <at> debbugs.gnu.org
Subject: Re: bug#5999: new snapshot available: coreutils-8.4.100-81926
Date: Tue, 27 Apr 2010 09:12:21 +0200
Gilles Espinasse wrote:
...
> I understand there is a problem but I am unsure of the direction to go.
> I made this stupid patch (attached) that include the same test than
> gl_cv_func_printf_directive_n in  coreutils sleep usage

You should be able to consider this resolved.
Once you start using the latest from gnulib,
you will no longer see that glibc diagnostic mixed in
with configure-output "checking..." messages.

> [chroot-i486] root:/usr/src/coreutils-8.5$ gl_cv_func_printf_directive_n=no
> ./configure --prefix=/usr
> [chroot-i486] root:/usr/src/coreutils-8.5$ make
> [chroot-i486] root:/usr/src/coreutils-8.5$ ./src/sleep; echo $?
> ./src/sleep: missing operand
> Try `./src/sleep --help' for more information.
> *** %n in writable segment detected ***
> Aborted
> 134
> [chroot-i486] root:/usr/src/coreutils-8.5$ make clean
> [chroot-i486] root:/usr/src/coreutils-8.5$ gl_cv_func_printf_directive_n=yes
> ./configure --prefix=/usr
> [chroot-i486] root:/usr/src/coreutils-8.5$ make
> [chroot-i486] root:/usr/src/coreutils-8.5$ ./src/sleep; echo $?
> ./src/sleep: missing operand
> Try `./src/sleep --help' for more information.
> *** %n in writable segment detected ***
> Aborted
> 134
>
> So result is the same with gl_cv_func_printf_directive_n=no or
> gl_cv_func_printf_directive_n=yes.
> Am I wrong somewhere?
> What is the gain that this test is so written?

The success or failure of that test contributes
to whether a project uses the native vasnprintf (because
it passes all tests) or a replacement.
See the many conditions in gnulib/m4/vasnprintf-posix.m4.




This bug report was last modified 15 years and 26 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.