On 4/24/10, Gilles Espinasse <g....@free.fr> 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.
> http://sourceware.org/bugzilla/show_bug.cgi?id=9854
>
> Gilles
>
>
Does this cause any configure tests to fail that should otherwise succeed?
--
Kevin Day
--
http://linuxfromscratch.org/mailman/listinfo/hlfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
