Subject: Re: Getting the PID in CLISP From: Erik Naggum <firstname.lastname@example.org> Date: 23 Oct 2002 21:42:54 +0000 Newsgroups: comp.lang.lisp Message-ID: <email@example.com> * "Johannes Grødem" <joh...@ifi.uio.no> | That's odd. Both 2.30 and the CVS-version builds just fine for me on | Debian 3.0. This had to happen. As instructed, I did the following: tar --gzip --extract --file=/home/gnu/clisp/release/clisp-2.30.tar.gz CC="gcc-3.2 -ansi" configure --quiet --build gcc-3.2-sans-syscalls At the end of a really logorrheic display we find some real meat: gcc-3.2 -ansi -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -fomit-frame-pointer -Wno-sign-compare -O2 -fexpensive-optimizations -DUNICODE -DDYNAMIC_FFI -c spvw.c In file included from unix.d:163, from lispbibl.d:1754, from spvw.d:22: /usr/include/sys/ipc.h:25:3: warning: #warning "Files using this header must be compiled with _SVID_SOURCE or _XOP EN_SOURCE" In file included from lispbibl.d:1754, from spvw.d:22: unix.d:244: warning: type defaults to `int' in declaration of `sigset_t' unix.d:244: parse error before '*' token unix.d:246: parse error before '*' token unix.d:249: parse error before '*' token In file included from lispbibl.d:1754, from spvw.d:22: unix.d:651: parse error before "caddr_t" In file included from spvw.d:22: lispbibl.d:7183: warning: register used for two global register variables In file included from spvw.d:521: spvw_sigsegv.d: In function `stackoverflow_handler': spvw_sigsegv.d:75: dereferencing pointer to incomplete type In file included from spvw.d:524: spvw_sigint.d: In function `react_on_sigint': spvw_sigint.d:61: `SIG_UNBLOCK' undeclared (first use in this function) spvw_sigint.d:61: (Each undeclared identifier is reported only once spvw_sigint.d:61: for each function it appears in.) In file included from spvw.d:525: spvw_sigwinch.d: In function `update_linelength': spvw_sigwinch.d:35: `caddr_t' undeclared (first use in this function) In file included from spvw.d:530: spvw_garcol.d: In function `gar_col_normal': spvw_garcol.d:1595: `SIG_BLOCK' undeclared (first use in this function) spvw_garcol.d:2097: `SIG_UNBLOCK' undeclared (first use in this function) In file included from spvw.d:530: spvw_garcol.d: In function `gar_col_compact': spvw_garcol.d:2359: `SIG_BLOCK' undeclared (first use in this function) spvw_garcol.d:2437: `SIG_UNBLOCK' undeclared (first use in this function) make: *** [spvw.o] Error 1 Please note that I have /zero/ interest in figuring out what went wrong. If you have any interest in making it work, let me know, and I can send you the entire output and all constructed files. I maintain that if you release something as open source, making use of existing facilities to configure, build, and install it is the baseline for comparisons. | Maybe "apt-get build-dep clisp" will fix it for you. I am not interested in help on building it. Christ, I thanked the people who took time out of their lives to build Debian packages. What I wanted to do was to build the packages from scratch so I had some control over the build parameters. You may have noticed that the CLISPs I have used have included a getpid function and others have not been so fortunate. So building the packages like the Debian maintainer does would obviously not help me understand what others would /not/ get. However, each of 2.27, 2.28, 2.29, and 2.30 bombed in various ways when the tarball was unrolled and the configure script was run in prescribed ways. When all four releases refused to build out of the box, my SIGWTF had maintained a steady high throughout and the only way to get rid of it was to scrap the "build from scratch to see what happened" project. Others have reported to me by mail that they had given up on CLISP for similar reasons and were relieved that it was not their fault they could not make it work. This should be taken seriously by the CLISP gang. -- 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.