From: Sam S. <sd...@gn...> - 2010-04-30 14:22:39
|
Faré wrote: > POIU used to work on CLISP, but something on current debian clisp > breaks it - probably some SIGCHLD handler or library function eating > the results from waitpid - do you know if such a thing is happening, > and if so is there an API to catch the pids? I am sorry, I do not understand what you are talking about. Maybe you could supply a test case? > The documentation seems to suggest --with-module=glibc but > --with-module is not recognized. Am I doing something wrong? clisp comes with the file INSTALL in the top-level directory. you mention debian, so clisp/INSTALL would refer you to clisp/unix/INSTALL which contains detailed, step-by-step instructions. E.g., 12. If you are lazy and have too few spare neurons to remember this long process, just use the shortcut, like I do: ./configure --with-module=rawsock --cbc build-dir this covers the build process through step 8 (except mod-check). > What's > the correct way to configure clisp to have all the modules possible > compiled in? you cannot "compile in" all modules because some are platform-specific (e.g., bindings/win32 and bindings/glibc) and some conflict with each other (e.g., clx/mit-clx and clx/new-clx) use "./configure --help-modules" to get the list of available modules. Sam. |