[PATCH] Fix bugs in test script silent5.test.

This tiny patch fix a nasty bug in 'silent5.test' (due to the use of grep instead of egrep) that could have lead to false negatives. The bug was introduced in one of my previous patches ("Improved test silent5.test", de09b369b135b971bffb0efe383716237b9bf7f1). In hindsight, a somewhat ironic sum

Re: [PATCH 0/2] Bugfix w.r.t. $(AM_LFLAGS)/$(LFLAGS) and $(AM_YFLAGS)/$(YFLAGS) precedence.

Hello Ralf. At Monday 21 June 2010, Ralf Wildenhues wrote: > I'm putting them in a new branch off of maint, and adding the > following patch below to fix a couple of nits in them. > I'm merging the branch to master for now, might merge to > branch-1.11 later as well, I'm not quite sure yet.

Re: [PATCH] Improve and extend test cond5.test.

Hello Ralf. May I ping this? If you think the patch is OK, I'd like to see it applied, since at present I'm continuing to experience annoying spurious failures in cond5.test. Thanks, Stefano

[PATCH 3/?, 4/?] Make sure all tests needing a C compiler require it explicitly

And here are the last two patches which should complete the first step of making the Automake testsuite more easy to run with different compilers. Regards, Stefano -*-*-*- Make sure all tests needing a C compiler require it explicitly. The list of the test scripts which needed a C compile

[PATCH 2/?] Do not SKIP a test on a command failing with `77' exit status (was: [PATCH] New requirement "cc" for tests using a C compiler)

At Tuesday 22 June 2010, Stefano Lattarini wrote: > > Next step will be to run the whole automake testsuite with > > `CC=no', to see which tests need a C compiler without explicitly > > requiring it. > > Which obviously doesn't help, because a configure script containing > the expansion of AC_PRO