> Hi,
>
> two days ago, I tried to compile CLISP 2.27 on my NetBSD-1.5.1 -mac68k
> machine.
>
> Unfortunately, I didn't even make it through the configure script, and -
> even worse - the configure script was the first thing to really blow up
> my system with a Kernel panic: Out of address space, when 'checking for
> working mmap'.
>
> Did anyone have the same problems, and maybe solved them?
I haven't, but I have had trouble with mmap on BSD machines before
(exercising it caused a kernel panic). Did you try ./configure
--help, to see if there's a way to force no mmap? Also, the clisp
list might be a good place to ask (I think it's clisp-list at lists
dot sourceforge dot org).
To disable the mmap test, try
env cl_cv_func_mmap_works=no ./configure
However, first check out
src/conftest.c
src/confdefs.h
src/config.log
which (after the crash-and-burn configure) should contain the
program which caused kernel panic, as well as a the log of - um,
maybe everything up to and _not_ including the command which
caused the trouble, since it crashed so thoroughly:-(
Anyway, if you can run that outside configure and get a panic, you
can send a Netbsd bug report which is far easier to reproduce.
> the clisp list might be a good place to ask (I think it's clisp-list
> at lists dot sourceforge dot org).
Yup. It's the bug-report address too, so mail them even if you work
around the problem.
--
Hallvard
>Unfortunately, I didn't even make it through the configure script, and -
>even worse - the configure script was the first thing to really blow up
>my system with a Kernel panic: Out of address space, when 'checking for
>working mmap'.
You better ask this in CLISP mailing list. See at
http://clisp.sourceforge.net/