Re: test failed

2000-05-30 Thread Gary V. Vaughan
On Mon, May 29, 2000 at 11:29:15PM -0500, Mocha wrote: > # make check | grep FAIL > FAIL: demo-exec.test > FAIL: demo-exec.test > FAIL: demo-exec.test > FAIL: hardcode.test > FAIL: build-relink.test > > that was on NetBSD-1.4Y/Alpha (ELF) and libtool 1.3.5. how can in find out > why the test fai

Re: test failed

2000-05-30 Thread Patrick Welche
On Tue, May 30, 2000 at 03:23:09PM +0200, Linus Nordberg wrote: > Mocha <[EMAIL PROTECTED]> wrote > Mon, 29 May 2000 23:29:15 -0500: > ># make check | grep FAIL >FAIL: demo-exec.test >FAIL: demo-exec.test >FAIL: demo-exec.test >FAIL: hardcode.test >FAIL: build-relink.test

Re: test failed

2000-05-30 Thread Alexandre Oliva
On May 30, 2000, Mocha <[EMAIL PROTECTED]> wrote: > how can in find out why the test failed and track down the errors. Start with defining the environment variable VERBOSE, so that you get more details about the errors. This might be a symptom of a bug that was fixed yesterday in the CVS tree,

Re: test failed

2000-05-30 Thread Linus Nordberg
Mocha <[EMAIL PROTECTED]> wrote Mon, 29 May 2000 23:29:15 -0500: # make check | grep FAIL FAIL: demo-exec.test FAIL: demo-exec.test FAIL: demo-exec.test FAIL: hardcode.test FAIL: build-relink.test that was on NetBSD-1.4Y/Alpha (ELF) and libtool 1.3.5. how can in find o