Re: [PATCH 2/6] Testsuite: fix missing*.test for non-default autotools.

2010-08-21 Thread Stefano Lattarini
On Saturday 21 August 2010, Ralf Wildenhues wrote: > * Stefano Lattarini wrote on Sat, Aug 21, 2010 at 01:00:46PM CEST: > > On Saturday 21 August 2010, Ralf Wildenhues wrote: > > > What is the actual problem by the way? > > > > Basically, `missing --run /abs/path/to/autoconf' does not > > recogniz

Re: [PATCH 2/6] Testsuite: fix missing*.test for non-default autotools.

2010-08-21 Thread Ralf Wildenhues
* Stefano Lattarini wrote on Sat, Aug 21, 2010 at 01:00:46PM CEST: > On Saturday 21 August 2010, Ralf Wildenhues wrote: > > What is the actual problem by the way? > Basically, `missing --run /abs/path/to/autoconf' does not recognize > the program being run as an "autoconf": Why not adjust `missing

Re: [PATCH 2/6] Testsuite: fix missing*.test for non-default autotools.

2010-08-21 Thread Stefano Lattarini
On Saturday 21 August 2010, Ralf Wildenhues wrote: > Hi Stefano, > > * Stefano Lattarini wrote on Thu, Aug 19, 2010 at 02:57:04PM CEST: > > * tests/missing.test: Build and use our own `autoconf' script, to > > avoid spurious failures due to configure-time value of $AUTOCONF > > being an absolute p

Re: [PATCH 2/6] Testsuite: fix missing*.test for non-default autotools.

2010-08-21 Thread Ralf Wildenhues
Hi Stefano, * Stefano Lattarini wrote on Thu, Aug 19, 2010 at 02:57:04PM CEST: > * tests/missing.test: Build and use our own `autoconf' script, to > avoid spurious failures due to configure-time value of $AUTOCONF > being an absolute path. Prefer passing overrides to ./configure > on the command