glibc _FORTIFY_SOURCE=2 and %n in writable segment detected

Kevin Day thekevinday at
Sat Apr 24 06:47:43 PDT 2010

On 4/24/10, Gilles Espinasse <g.esp at> wrote:
> Some packages actually coreutils-8.{4,5}, gzip-1.4, m4-1.4.14 print a
>  spurious
>  "%n in writable segment detected" message during configure when glibc is
>  compiled with _FORTIFY_SOURCE=2
>  This result in gl_cv_func_printf_directive_n=no.
>  If we want to be able to control where the message is printed, we need to
>  add to the configure command
>  LIBC_FATAL_STDERR_=1 ./configure
>  That way, the message is redirected to stderr as usual.
>  Gilles

Does this cause any configure tests to fail that should otherwise succeed?

Kevin Day

More information about the hlfs-dev mailing list