Re: Problem with fstatat on AIX 7.1

2011-08-30 Thread Paul Eggert
On 08/19/11 12:31, Kevin Brott wrote: > Return code on that as compiled comes back as "1" . OK, thanks, to move forward on that part, I installed the following patch into gnulib. I'll look at the other tar problems later. openat: work around AIX 7.1 fstatat bug Problem reported by Kevin Brott f

Re: valgrind-tests.m4 is not compatible with libtool

2011-08-30 Thread Bruno Haible
Hi Vincent, > valgrind-tests.texi says: > > However, this means that binaries invoked through scripts will not be > invoked under valgrind, which could be solved by adding the following: > > @smallexample > TESTS_ENVIRONMENT = VALGRIND='$(VALGRIND)' > @end smallexample > > And then modify the s

valgrind-tests.m4 is not compatible with libtool

2011-08-30 Thread Vincent Lefevre
Hi, I've just done a test with the GNU MPC trunk, which is now based on valgrind-tests.m4, and this is not compatible with libtool, because it generates wrapper scripts. valgrind-tests.texi says: However, this means that binaries invoked through scripts will not be invoked under valgrind, which

Re: Fix compilation of strerror-override with llvm/clang

2011-08-30 Thread Aleksander Morgado
Hey Bruno, > > So I have to ask: > - What is your platform? > - What are the values of $CC, $CFLAGS, $CPPFLAGS that you are using in your > configuration? > - More precisely, how to reproduce the problem you had? > - Does the problem go away if you do a "make distclean" and reconfigur

Re: Infinite recursion with fopen

2011-08-30 Thread Bruno Haible
Michael Goffioul wrote: > Yes, it fixes the problem, thanks. Note that a similar problem may occur > in open.c Thanks for testing. I've applied this patch: 2011-08-30 Bruno Haible Avoid endless recursions if config.h includes some header files. * lib/fopen.c (__need_FILE): De

Re: Fix compilation of strerror-override with llvm/clang

2011-08-30 Thread Bruno Haible
Hi Aleksander, > I'm compiling gnupdf under llvm/clang; and found an issue with the > strerror-override module. In my setup, it defines strerror_override() to > NULL in the .h file, but then it implements the method anyway in the .c > file, and llvm/clang doesn't like that: > > strerror-o