Re: test failed
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, in the test of whether the library format was ELF or a.out. -- Alexandre OlivaEnjoy GuaranĂ¡, see http://www.ic.unicamp.br/~oliva/ Cygnus Solutions, a Red Hat companyaoliva@{redhat, cygnus}.com Free Software Developer and EvangelistCS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org} Write to mailing lists, not to me
Re: test failed
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 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. Stop") Just to follow up, that would mean gmake MAKE=gmake VERBOSE=yes check if you have (as I do) GNU make installed as gmake, and with NetBSD-1.4Z/i386, cvs libtool from just now, I just have the following fail: FAIL: depdemo-exec.test FAIL: depdemo-inst.test FAIL: depdemo-exec.test FAIL: depdemo-inst.test FAIL: depdemo-exec.test FAIL: depdemo-inst.test FAIL: build-relink2.test The gory detail can be found at http://www.newn.cam.ac.uk/prlw/NetBSD/libtoolerrs.txt Cheers, Patrick
Re: test failed
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 and track down the errors. Going through the tests one at a time you can do this: $ cd libtool-1.3.5/tests $ VERBOSE=1 make check TESTS='some-test.test' However, some of the tests depend on other tests having been run immediately beforehand, and the `demo-exec' test for example is reused in several contexts -- you must look at the full output of make check, and list the preceding tests too: $ VERBOSE=1 make check TESTS='demo-foo.test demo-bar.test demo-exec.test' That should get you going... AN IMPORTANT NOTE: ** I now consider the 1.3.x branch to be dead, and will be concentrating on the cvs trunk (1.3c) in preparation for a 1.4 release as soon as possible. So you might want to run these checks with a cvs snapshot from ffii.org (libtool homepages explain how to get these). I have made a fair number of *BSD related changes to the HEAD revision in the last few days -- none of which I can test, so your feedback would be very much appreciated. On the other hand any useful looking stuff you submit against 1.3.5 might be gratuitously ported to CVS HEAD =)O| Cheers, Gary. -- ___ _ ___ __ _ mailto: [EMAIL PROTECTED] / __|__ _ _ ___ _| | / / | / /_ _ _ _ __ _| |_ __ _ ___ [EMAIL PROTECTED] | (_ / _` | '_|// / |/ /| |/ / _` | || / _` | ' \/ _` | _ \ \___\__,_|_|\_, /|___(_)___/\__,_|\_,_\__, |_||_\__,_|//_/ home page: /___/ /___/ gpg public key: http://www.oranda.demon.co.uk http://www.oranda.demon.co.uk/key.asc
test failed
# 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.