glibc _FORTIFY_SOURCE=2 and %n in writable segment detected

Gilles Espinasse g.esp at free.fr
Sat Apr 24 00:36:37 PDT 2010


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.
http://sourceware.org/bugzilla/show_bug.cgi?id=9854

Gilles




More information about the hlfs-dev mailing list