[test failure] Re: t4114 binary file becomes symlink

[Nicolas Sebrecht <nicolas.s.dev@gmx.fr>]

The 18/07/09, Nicolas Sebrecht wrote:
> The 18/07/09, Johannes Sixt wrote:
> > On Samstag, 18. Juli 2009, Nicolas Sebrecht wrote:
> > > ==10807== Process terminating with default action of signal 11 (SIGSEGV)
> > > ==10807==  Access not within mapped region at address 0x1
> > > ==10807==    at 0x4C22349: strlen (in
> > > /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so) ==10807==    by
> > > 0x5616ED6: vfprintf (in /lib64/libc-2.8.so)
> > > ==10807==    by 0x563C159: vsnprintf (in /lib64/libc-2.8.so)
> > > ==10807==    by 0x495E90: git_vsnprintf (snprintf.c:38)
> > > ==10807==    by 0x48917B: strbuf_addf (strbuf.c:203)
> > 
> > amd64-linux, and you build with SNPRINTF_RETURNS_BOGUS? Why do you have this 
> > option set?
> 
> I don't tune any flags myself and
> 
>   $ printf "$CC\n $CFLAGS\n $LDFLAGS\n $LIBS\n $CPPFLAGS\n $CPP\n"
> 
> is empty. Is there another way to accidentally set a flag other than
> environment variables or options to 'make'?

Hum, 'rm configure ; make configure ; ./configure' give

 checking whether snprintf() and/or vsnprintf() return bogus value... yes

WTF?

-- 
Nicolas Sebrecht