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 Patrick Welche
that was on NetBSD-1.4Y/Alpha (ELF) and libtool 1.3.5. how can in find out why the test failed and track down the errors. Try $ make VERBOSE=yes check Are you using GNU make? I have lots of failures when using system make on a FreeBSD-3.3 system. ("make: don't know how to make w.

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 failed

test failed

2000-05-29 Thread Mocha
# 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 failed and track down the errors.