Subject: Re: bug#5999: new snapshot available: coreutils-8.4.100-81926

From: Jim Meyering <[email-masked]>
Date: Tue, 27 Apr 2010 09:04:18 +0200

Bruno Haible wrote:
> Paolo Bonzini wrote:
>> > Here's a patch to make that diagnostic go where it belongs
>> > for all gnulib-using projects:
>>
>> I wonder if we shouldn't do that for all _autoconf_-using projects!
>
> Or, at least, for all tests in all gnulib-using projects. There are
> more possible causes of a FORTIFY message, according to
>   <https://wiki.edubuntu.org/CompilerFlags>
>
> How about this proposed patch?

I like it.  Thanks.
Adjusted and pushed like this:

...
+2010-04-26  Jim Meyering  <[email-masked]>
+	    Bruno Haible  <[email-masked]>
+
+	gnulib-common.m4: make glibc write diagnostics to stderr, not /dev/tty
+	* m4/gnulib-common.m4 (gl_COMMON_BODY): Set LIBC_FATAL_STDERR_.
+	Prompted by an exchange with Gilles Espinasse.
+
 2010-04-26  Jim Meyering  <[email-masked]>

 	git-version-gen: aesthetic tweak
diff --git a/m4/gnulib-common.m4 b/m4/gnulib-common.m4
index 54b2517..4c7ac30 100644
--- a/m4/gnulib-common.m4
+++ b/m4/gnulib-common.m4
@@ -1,4 +1,4 @@
-# gnulib-common.m4 serial 19
+# gnulib-common.m4 serial 20
 dnl Copyright (C) 2007-2010 Free Software Foundation, Inc.
 dnl This file is free software; the Free Software Foundation
 dnl gives unlimited permission to copy and/or distribute it,
@@ -35,6 +35,12 @@ AC_DEFUN([gl_COMMON_BODY], [
    is a misnomer outside of parameter lists.  */
 #define _UNUSED_PARAMETER_ _GL_UNUSED
 ])
+  dnl Preparation for running test programs:
+  dnl Tell glibc to write diagnostics from -D_FORTIFY_SOURCE=2 to stderr, not
+  dnl to /dev/tty, so they can be redirected to log files.  Such diagnostics
+  dnl arise e.g., in the macros gl_PRINTF_DIRECTIVE_N, gl_SNPRINTF_DIRECTIVE_N.
+  LIBC_FATAL_STDERR_=1
+  export LIBC_FATAL_STDERR_
 ])

 # gl_MODULE_INDICATOR_CONDITION
--
1.7.1.328.g9993c