From: Louis M. <lm...@lo...> - 2007-07-15 17:06:22
Attachments:
smime.p7s
|
Hello, My make check fails (23 out of 25 tests) when trying to build bashdb-3.1-0.08. I've succesfully installed it on debian stable but OS X (10.4) seems reluctant to allow me the bliss of debugging in emacs... A bit of background: - I have installed readline 5.2, bash 3.2 and emacs 22.1 from source in /usr/local/ (but I have started with $EMACS undefined to see if it would compile with the default emacs 21 in /usr/bin/emacs, changing $EMACS to /usr/local/bin/emacs doesn't seems to make any difference anyway, make check still fails). - Last 10 lines of make-check.log (2619 more available if needed): +Breakpoint 1 hit (1 times). +(dbg-test1.sh:17): +17: fn3() { + 0 (echo "x is $x, ? is $?"): x is 29, ? is 0 ++ quit FAIL: run-watch2 =================================================== 23 of 25 tests failed Please report to bas...@li... =================================================== Any help much appreciated... Louis |
From: Rocky B. <roc...@gm...> - 2007-07-15 17:33:55
|
I don't see enough information on the failure to give anything but general suggestions. The most obvious one is to pay attention to warnings and messages that appear when you run "configure" "make" and of course "make test". >From the output below I see that one of the test programs that failed is called run-watch2. It should be located in a directory called "test". Run that single program (run-watch2) from the directory it is located in. The idea of that test program and others is to run a sequence of debuggers commands and compare the output against known good output. Good luck! On 7/15/07, Louis Munro <lm...@lo...> wrote: > > Hello, > My make check fails (23 out of 25 tests) when trying to build > bashdb-3.1-0.08. > I've succesfully installed it on debian stable but OS X (10.4) seems > reluctant to allow me the bliss of debugging in emacs... > > A bit of background: > - I have installed readline 5.2, bash 3.2 and emacs 22.1 from source in > /usr/local/ (but I have started with $EMACS undefined to see if it would > compile with the default emacs 21 in /usr/bin/emacs, changing $EMACS to > /usr/local/bin/emacs doesn't seems to make any difference anyway, make > check still fails). > > - Last 10 lines of make-check.log (2619 more available if needed): > +Breakpoint 1 hit (1 times). > +(dbg-test1.sh:17): > +17: fn3() { > + 0 (echo "x is $x, ? is $?"): x is 29, ? is 0 > ++ quit > FAIL: run-watch2 > =================================================== > 23 of 25 tests failed > Please report to bas...@li... > =================================================== > > Any help much appreciated... > > Louis > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Bashdb-devel mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-devel > > > |
From: Rocky B. <roc...@gm...> - 2007-07-16 02:30:10
|
This message bashdb: cannot read . Perhaps bashdb is installed wrong. means bashdb can't read the directory where it thinks bashdb is (temporarily) installed. The -L option allows one to indicate where this directory is. See around line 209 of the bashdb script. I'll change the wording on this error message to try to be more clear. So in essence all of the tests are failing.. Sometimes this happens when the "build" directory location is set incorrectly. There's lots of autotools configuration magic that's supposed to make that work, but how to use autoconf/automake has always been a great mystery to me. In this regard I generally use the Make Debugger/tracer (remake) that I wrote to help me figure out what's going on, e.g. why the makefile thinks "." is the build directory, etc. On 7/15/07, Louis Munro <lm...@lo...> wrote: > > Rocky Bernstein wrote: > > I don't see enough information on the failure to give anything but > > general suggestions. The most obvious one is to pay attention to > > warnings and messages that appear when you run "configure" "make" and > > of course "make test". > > > > From the output below I see that one of the test programs that failed is > > called run-watch2. It should be located in a directory called "test". > > Run that single program (run-watch2) from the directory it is located > > in. The idea of that test program and others is to run a sequence of > > debuggers commands and compare the output against known good output. > > > > Good luck! > > > > Ok, here are (attached) the complete outputs of ./configure, make and > make check. Hope that helps. > The only thing that sticks out is this in make-check.log: > -bashdb: cannot read . Perhaps bashdb is installed wrong. > -bashdb: or try using -L (with a different directory). > > bashdb isn't installed yet (I haven't run make install because of the > errors) and all files in this directory are readable. > > Thanks for your help [log output deleted] |