From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: Getting the PID in CLISP Date: 23 Oct 2002 15:12:36 +0000 Organization: Naggum Software, Oslo, Norway Lines: 18 Message-ID: <3244374756040130@naggum.no> References: <3244311909148921@naggum.no> <3DB5EB2E.641A07A9@enterprise.net> <3244322069487950@naggum.no> <3DB6A39D.A4E1DB47@enterprise.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: maud.ifi.uio.no 1035385957 1322 129.240.65.5 (23 Oct 2002 15:12:37 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 23 Oct 2002 15:12:37 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:44398 * Donald Fisk | I use: | | Command: clisp --version | CLISP 1999-07-22 (July 1999) The crucial element appears to be whether you compile with exported syscalls or not. I have just tried to build 2.27, 2.28, 2.29, and 2.30 from the distributed tarballs, but all of them bomb during building, so I gave up on recovering the configuration options necessary to get `getpidĀ“ in, e.g., the LINUX package. My heartfelt thanks go out to the people who take time out of their lives to build CLISP into Debian packages. -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.