Re: FAIL: make.test

2002-02-20 Thread Patrick Welche
On Sun, Feb 17, 2002 at 06:48:13PM -0700, Tom Tromey wrote: > > "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes: > > adl> I managed to reproduce this (on NetBSD 1.5.2), and reduced the > adl> failure to the following script: > > adl> % cat foo.sh > adl> set -e > adl> for x in a; do

Re: FAIL: make.test

2002-02-17 Thread Tom Tromey
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes: adl> I managed to reproduce this (on NetBSD 1.5.2), and reduced the adl> failure to the following script: adl> % cat foo.sh adl> set -e adl> for x in a; do adl>BAR="foo" adl>false && echo true adl>echo mumble adl> done

Re: FAIL: make.test

2002-02-15 Thread Patrick Welche
Scrap my earlier mumblings and the patch! Having been put right again by Christos: When this option is on, if a simple command fails for any of the reasons listed in Consequences of Shell Errors or returns an exit status value >0, and is not part of the compound list following a while, until, or

Re: FAIL: make.test

2002-02-14 Thread Patrick Welche
On Thu, Feb 14, 2002 at 04:36:36PM +0100, Alexandre Duret-Lutz wrote: > I managed to reproduce this (on NetBSD 1.5.2), and reduced the > failure to the following script: > > % cat foo.sh > set -e > for x in a; do >BAR="foo" >false && echo true >echo mumble > done > % sh -x foo.sh > +

Re: FAIL: make.test

2002-02-14 Thread Alexandre Duret-Lutz
I managed to reproduce this (on NetBSD 1.5.2), and reduced the failure to the following script: % cat foo.sh set -e for x in a; do BAR="foo" false && echo true echo mumble done % sh -x foo.sh + set -e + BAR=foo + false This ought to print "mumble". It does so if you remove the loop or

Re: FAIL: make.test

2002-02-13 Thread Patrick Welche
On Wed, Feb 13, 2002 at 06:54:07PM +0100, Alexandre Duret-Lutz wrote: > > Patrick> config.status: creating Makefile > Patrick> + fgrep am__include = # Makefile > Patrick> FAIL: make.test > > So, what does this Makefile contains? > > Could you run > grep

Re: FAIL: make.test

2002-02-13 Thread Patrick Welche
On Wed, Feb 13, 2002 at 09:31:19PM +0100, Alexandre Duret-Lutz wrote: > Nope, this code comes from Automake, and `am__include = include' > is the expected output. > > The question is why does > > fgrep 'am__include = #' Makefile && exit 1 > > abort the test? > > Can you check how the followi

Re: FAIL: make.test

2002-02-13 Thread Alexandre Duret-Lutz
>>> "Patrick" == Patrick Welche <[EMAIL PROTECTED]> writes: Patrick> On Wed, Feb 13, 2002 at 06:54:07PM +0100, Alexandre Duret-Lutz wrote: >> Patrick> config.status: creating Makefile Patrick> + fgrep am__include = # Makefile Patrick> FAIL: mak

Re: FAIL: make.test

2002-02-13 Thread Alexandre Duret-Lutz
>>> "Patrick" == Patrick Welche <[EMAIL PROTECTED]> writes: [...] Patrick> config.status: creating Makefile Patrick> + fgrep am__include = # Makefile Patrick> FAIL: make.test So, what does this Makefile contains? Could you run grep am__include /usr/s

Re: FAIL: make.test

2002-02-13 Thread Patrick Welche
no checking for awk... awk checking whether gmake sets ${MAKE}... yes checking for style of include used by gmake ... GNU configure: creating ./config.status config.status: creating Makefile + fgrep am__include = # Makefile FAIL: make.test === 1 of 1 tests failed ==

Re: FAIL: make.test

2002-02-13 Thread Alexandre Duret-Lutz
>>> "Patrick" == Patrick Welche <[EMAIL PROTECTED]> writes: [...] Patrick> Hints on where to delve/how to fix? Yep: could you run the same test with VERBOSE=x? i.e. gmake check TESTS=make.test VERBOSE=x -- Alexandre Duret-Lutz

FAIL: make.test

2002-02-13 Thread Patrick Welche
checking for awk... awk checking whether gmake sets ${MAKE}... yes checking for style of include used by gmake ... GNU configure: creating ./config.status config.status: creating Makefile FAIL: make.test === 1 of 1 tests failed === gmake[1]: *** [check-TESTS] Error 1 gmake