Bug 39303 – clisp 2.31-r1 fails to compile

• Product: Gentoo Linux
• Status: RESOLVED TEST-REQUEST

[Description Javier Fernandez-Ivern 2004-01-24 19:38:16 UTC]

make[2]: Entering directory `/var/tmp/portage/clisp-2.31-r1/work/clisp-2.31/build/callback/trampoline_r'
/bin/sh ./libtool --mode=compile gcc -march=i686 -O2 -fomit-frame-pointer -pipe -g -O2 -I. -I../../../ffcall/callback/trampoline_r -c ../../../ffcall/callback/trampoline_r/trampoline.c
gcc -march=i686 -O2 -fomit-frame-pointer -pipe -g -O2 -I. -I../../../ffcall/callback/trampoline_r -c ../../../ffcall/callback/trampoline_r/trampoline.c -o trampoline.o
../../../ffcall/callback/trampoline_r/trampoline.c: In function `alloc_trampoline_r':
../../../ffcall/callback/trampoline_r/trampoline.c:455: `MAP_VARIABLE' undeclared (first use in this function)
../../../ffcall/callback/trampoline_r/trampoline.c:455: (Each undeclared identifier is reported only once
../../../ffcall/callback/trampoline_r/trampoline.c:455: for each function it appears in.)
make[2]: *** [trampoline.lo] Error 1
make[2]: Leaving directory `/var/tmp/portage/clisp-2.31-r1/work/clisp-2.31/build/callback/trampoline_r'
make[1]: *** [all-subdirs] Error 2
make[1]: Leaving directory `/var/tmp/portage/clisp-2.31-r1/work/clisp-2.31/build/callback'
make: *** [callback.h] Error 2

!!! ERROR: dev-lisp/clisp-2.31-r1 failed.
!!! Function src_compile, Line 82, Exitcode 2
!!! (no error message)

This builds fine on my athlon-xp machine with 2.6 headers, and breaks here (2.4 headers, pentium 3).  I've tried lowering my CFLAGS to -march=i686 and it still breaks like this.

Reproducible: Always
Steps to Reproduce:
1. emerge clisp
2.
3.




root@kestrel root # emerge info
Portage 2.0.49-r20 (hardened-x86-1.4, gcc-3.2.3, glibc-2.3.2-r9, 2.4.22-hardened)
=================================================================
System uname: 2.4.22-hardened i686 Pentium III (Katmai)
Gentoo Base System version 1.4.3.10
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-march=i686 -O2 -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /usr/share/texmf/tex/generic/config/
/usr/share/texmf/tex/platex/config/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-march=i686 -O2 -fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox sfperms strict"
GENTOO_MIRRORS="http://www.gtlib.cc.gatech.edu/pub/gentoo
ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo"
MAKEOPTS=""
PKGDIR="/usr/local/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="apache2 berkdb crypt curl gdbm imap ipv6 java libwww maildir mysql ncurses
nls pam perl pic python readline sasl slang spell ssl tcpd tetex x86 xml xml2 zlib"

[Comment 1 Matthew Kennedy (RETIRED) 2004-01-26 11:19:59 UTC]

please try clisp-2.32-r1. since you're on arch and not ~arch, issue:

   ACCEPT_KEYWORDS='~x86' emerge clisp --pretend

If it works, please let me know.

[Comment 2 Javier Fernandez-Ivern 2004-01-26 17:36:57 UTC]

Seemes to have fixed it, but now I get the following error.  I think this is due to hardened gentoo, though...not clisp.  Any ideas?

cd trampoline_r; make check
make[2]: Entering directory `/var/tmp/portage/clisp-2.32-r1/work/clisp-2.32/build/callback/trampoline_r'
./test1
trampoline: cannot make memory executable
make[2]: *** [check] Aborted
make[2]: Leaving directory `/var/tmp/portage/clisp-2.32-r1/work/clisp-2.32/build/callback/trampoline_r'
make[1]: *** [check-subdirs] Error 2
make[1]: Leaving directory `/var/tmp/portage/clisp-2.32-r1/work/clisp-2.32/build/callback'
make: *** [callback.h] Error 2
                                                                                
!!! ERROR: dev-lisp/clisp-2.32-r1 failed.
!!! Function src_compile, Line 84, Exitcode 2
!!! (no error message)

[Comment 3 Matthew Kennedy (RETIRED) 2004-01-28 23:24:53 UTC]

all bets are off if you're using hardened features.  i've had nothing but problems with lisp on these so called "hardened" platforms.