I guess, there is no a need to fix configure it works fine on all
systems I tried (linux with-dffi is ok), it was just not working on
mingw/msys/winxp because with-dffi was looking for a lbffi that comes
with mingw and that's not what ecl wants. So I reverted to add a small
old piece that was enabling dffi by default (ecl-version 0.9l I think).
And that worked just great. I guess one can just customize it for his
own build on mingw/msys/winxp.
But it's fine now. However "the Internal or unrecoverable error in: not
a lisp data object" after requiring asdf is troubling me. I tried to
use gdb to see why is that happening but couldn't get it to work
(what I did to try to debug was compile asdf.lisp with c-file t and
then I use gdb on ecl with: set breakpoint pending on and: break
asdf.c:(some line #) but when run, the system exists with the same
error message and doesn't even let me enter the debugger).
Note however that when I run ecl and use (compile-file "asdf.lisp") it
compiles ok and when I (load "asdf.fas") it loads and works fine. It's
only when I exit ecl and run it again and directly (load "asdf.fas")
that it gives the error!
Sent: Fri, Dec 31, 2010 5:08 pm
Subject: Re: MinGW build
ok fixed the dffi problem with a patch to src/configure (I had sent you
eralier). But now this:
ECL (Embeddable Common-Lisp) 10.7.1
Copyright (C) 1984 Taiichi Yuasa and Masami Hagiya
Copyright (C) 1993 Giuseppe Attardi
Copyright (C) 2000 Juan J. Garcia-Ripoll
ECL is free software, and you are welcome to redistribute it
under certain conditions; see file 'Copyright' for details.
Type :h for Help.
Top level in: #<process TOP-LEVEL>.
> (require 'asdf)
;;; Loading #P"C:/ecl/asdf.fas"
Internal or unrecoverable error in:
not a lisp data object
This application has requested the Runtime to terminate it in an
Please contact the application's support team for more information.
* Note that building on linux doesn't present this problem. only on