full/lisp.run -B . -M full/lispinit.mem -norc -q -i regexp/regexp syscalls/posix wildcard/wildcard bindings/glibc/linux bindings/glibc/wrap postgresql/postgresql -x (saveinitmem "full/lispinit.mem") ./clisp-link: line 550: 20305 Killed "$@" make: *** [full] Error 1 !!! ERROR: dev-lisp/clisp-2.33.2-r1 failed. Reproducible: Always Steps to Reproduce: emerge dev-lisp/clisp Actual Results: Unable to install dev-lisp/clisp due to emerge dying with the above error. emerge info Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.4.26-grsec i686) ================================================================= System uname: 2.4.26-grsec i686 Intel(R) Celeron(TM) CPU 1000MHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.1.3-r1,dev-lang/python-2.3.4,dev-lang/python-2.2.3-r5 [2.3.4 (#1, Jan 26 2005, 15:50:29)] dev-lang/python: 2.1.3-r1, 2.3.4, 2.2.3-r5 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.5, 1.7.9-r1, 1.6.3, 1.4_p6, 1.9.4, 1.8.5-r3 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.4.21-r1, 2.4.19-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=i386 -O2 -pipe" CHOST="i386-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=i386 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache digest distlocks sandbox sfperms strict userpriv" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 apm avi berkdb bitmap-fonts crypt cups encode esd f77 fam font-server foomaticdb fortran gd gdbm gif gtk gtk2 imagemagick imap imlib ipv6 java jpeg junit ldap libg++ libwww mad maildir mikmod motif mozilla mpeg ncurses oggvorbis oss pam pdflib perl png postgres quicktime readline sasl sdl slang snmp ssl tcltk tcpd tetex tiff truetype-fonts type1-fonts xml2 xmms xv zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
--> glibc-2.3.4.20040808-r1, 2.4.26-grsec i686) I think that you may encounter problems with GRSEC and CLISP/SBCL/CMUCL. If you try the same under a non-GRSEC kernel do you still encounter the same problem?
No problems with cmucl or sbcl - both emerged successfully on this same system & environment (did a full system rebuild before after switching from gcc 2.96 to gcc3 - had to remove the formerly working clisp install to get the world rebuild to finish). Both cmucl and sbcl run - as far as a few short tests determined - fine. Unfortunately, I can't test emerging clisp under a non-grsec kernel since this is a production system in a remote location where just rebooting and switching kernels around is not an option. My Gentoo testsystem (where I could try this) is currently unavailable due to hardware failure.
I did some further testing. Turns out, if I disable _all_ clisp modules in the ebuild (by removing all --with-module ... entries, disabling PostgreSQL-Support, disabling PCRE-Support), then clisp compiles and installs just fine. As soon as I enable one of the modules, emerging clisp dies as shown. Since my Lisp code does not use any of the clisp modules, this is currently a barely acceptable workaround, but I would prefer to have the ebuild work without resorting to this kind of ebuild butchery ;-)
(In reply to comment #0) > glibc-2.3.4.20040808-r1, 2.4.26-grsec i686) > ================================================================= > System uname: 2.4.26-grsec i686 Intel(R) Celeron(TM) CPU 1000MHz Hmm... I have the grsec patches, and pax to boot. What I get is this: make[2]: Entering directory `/var/tmp/portage/clisp-2.34-r1/work/clisp-2.34/build/callback/trampoline_r' ./test1 trampoline: cannot make memory executable I happen to know that pax has an option "EMUTRAMP" that has to do with something called a memory trampoline. But it could be grsec too, or even the pie, ssp and hardened patches to gcc. (Yes, I know, I'm paranoid.) I'm thinking your bug might be similar to mine, even though we got different error messages. Is there anyone who sees a connection between these two errors?
Update: the current dev-lisp/clisp-2.34-r1 emerges just fine and works.
