-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ralf Wildenhues on 11/23/2008 9:37 AM:
> * Eric Blake wrote on Sun, Nov 23, 2008 at 03:56:49PM CET:
>> According to Ralf Wildenhues on 11/23/2008 6:23 AM:
>>> running
>>> make check-local TESTSUITEFLAGS=-v
>>>
>>> on M4 (git master) prod
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Moulard on 4/13/2009 6:00 AM:
> About the "which" issue, Valgrind does not need an absolute path, it is just
> that I used to rely on the fact that my binaries are always in my PATH.
autotest can be made to guarantee that the binar
On Mon, Apr 13, 2009 at 1:49 PM, Eric Blake wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> According to Thomas Moulard on 4/12/2009 8:01 PM:
>> However, I still have an issue with the other scenario (MinGW
>> cross-compiling):
>> in that case, my binaries are suffixed with '.exe'.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thomas Moulard on 4/12/2009 8:01 PM:
> However, I still have an issue with the other scenario (MinGW
> cross-compiling):
> in that case, my binaries are suffixed with '.exe'.
>
> Is is easy to make Autotest aware of EXEEXT, however AT_TE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Mike Frysinger on 4/13/2009 4:40 AM:
>>> I just had to use "which" to force an absolute path as Valgrind does not
>> "which" probably isn't guaranteed to appear on every platform that
>> autoconf scripts might run on - ymmv
>
> nor is it
On Monday 13 April 2009 06:03:05 Thomas Dickey wrote:
> On Mon, 13 Apr 2009, Thomas Moulard wrote:
> > On Sat, Apr 11, 2009 at 1:21 PM, Eric Blake wrote:
> >> This is very doable. In fact, it is how the m4 testsuite allows the
> >> user to specify an alternate $SED program [1]. You can use atloc
On Mon, 13 Apr 2009, Thomas Moulard wrote:
On Sat, Apr 11, 2009 at 1:21 PM, Eric Blake wrote:
This is very doable. In fact, it is how the m4 testsuite allows the user
to specify an alternate $SED program [1]. You can use atlocal.in to
perform initialization of your $TESTSUITE_PREFIX before a
