Re: GSoC status report

[Daniel J. <dan...@gm...>]

Just a quick update:

Sam wrote:
> does GENERATIONAL_GC get enabled?

Yes, at least according to clisp --version.

Sam wrote:
>> Jörg wrote (regarding "64 bit support"):
>>> I'm confused. If on amd64, you're building a 64bit version, aren't you?
>>> So what doesn't get configured and what builds and passes tests?
>>
>> (on linux)
>> I'm on amd64, and am building a 64bit version. Both clisp and lisp.run are
>> 64bit elf executables. There's :WORD-SIZE=64 in *features*.
>
>(integer-length most-positive-fixnum) should return 48.

It does. I also found why I get those ffi errors:

"We" define HAVE_LONG_LONG_INT. It gets undefined in (at least my version of)
avcall.h, which contains this relatively at the top:

/* AC_TYPE_LONG_LONG */
/* Define if your compiler supports the 'long long' type. */
#undef HAVE_LONG_LONG_INT

/* End of definitions adjusted by `configure'. */

Since foreign.d includes avcall.h after including lispbibl.c, the ffi code
doesn't know that there's actually long long support.

Some first testing suggests that this is a bug in libffcall (I also suspected
my distribution, but am now pretty sure I ruled that out). HEAD of libffcall
defines HAVE_LONG_LONG_INT to 1 as it should on my system. (I was using
2009-05-27 previously.)


Regarding my issues with paths when building on windows: This is my fault,
I read configure and was assuming I could do an out-of-source build (e.g.
mkdir build; cd build; ../clisp/configure --srcdir=../clisp). I guess this
was a false assumption :)

I'm now doing as you suggested: passing a dir arg to the top level configure.