Re: Pari module build failure

Sam Steingold wrote:
> This is a relatively recent regression, "hg bisect" should be able to
> pinpoint the commit that broke it.

How do you use 'hg bisect' in practice? I've never used it. When a build
takes betwen 15 min and 2 h, I'd like to be sure I use the right commands
before starting a multi-hour build sequence.

> > ;; Loading file /builddir/build/BUILD/clisp-2.49.60/build/pari/desc2lisp.fas ...
> > *** - EXT:FINALIZE: #<address #x0000000000859E30> is not a function
> > make[1]: *** [Makefile:35: pari.c] Error 1
> >
> > What does that mean?
> 
> This stems from
> 
> --8<---------------cut here---------------start------------->8---
> > (regexp:regexp-compile "abc")
> *** - FINALIZE: #<ADDRESS #x0000000107B75918> is not a function
> --8<---------------cut here---------------end--------------->8---

Maybe in this case you can compile clisp with "-ggdb -O0" and get a
stack trace with gdb?

Bruno


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel