Hi Bruno. Thank you for fixing the interactions between
__printf__ in gnulib and libintl.
I have a followup question. While I was trying to figure out
whether PSPP could now drop its definition of DEPENDS_ON_LIBINTL
from its configure.ac, I noticed that there were references to
this preprocessor
Hi Ben,
* Ben Pfaff wrote on Thu, May 20, 2010 at 09:11:58PM CEST:
> Ralf Wildenhues writes:
>
> > That's quite bad. Maybe libtool should have a way to use valgrind only
> > on the "interesting" executable, not the rest of any wrappers, or the
> > libtool script, for efficiency reasons.
>
> To
Ralf Wildenhues writes:
> That's quite bad. Maybe libtool should have a way to use valgrind only
> on the "interesting" executable, not the rest of any wrappers, or the
> libtool script, for efficiency reasons.
To run valgrind on a program that might use libtool, I just use
libtool --mo
[ adding bug-libtool ]
* Bruno Haible wrote on Wed, May 19, 2010 at 11:12:08AM CEST:
> Simon Josefsson wrote:
> > my patch invokes valgrind with -q so that it does not
> > output anything, unless there are errors, of course
>
> Oh, I see. Indeed.
>
> But it spends a lot of time in "make check",
Ralf Wildenhues writes:
> Hi Simon,
>
> I like this patch, with one small nit:
>
> * Simon Josefsson wrote on Wed, May 19, 2010 at 08:41:29AM CEST:
>> +This will run all self-checks under valgrind. This can be wasteful if
>> +you have many shell scripts or other non-binaries. Using the Automake
