Menu
▾
▴
clisp-devel
|
From: Vladimir S. <vs...@gm...> - 2010-09-25 18:50:21
|
Tried building a CLISP I just pulled from CVS, on Debian 5. The installed version of libsigsegv didn't work (older version), followed directions to build and install libsigsegv-2.8, first with --prefix=/usr/local, then with --prefix=/ usr (default), neither were detected by the ./configure script (passed --with- libsigsegv-prefix parameter). I think the detection routine is in the aclocal.m4 script, but not sure. Can someone double-check this? Vladimir |
|
From: edgar <edg...@we...> - 2010-09-25 20:27:05
|
Hi Vladimir,
Tested on Debian 5 (lenny) just half an hour ago:
This is how I compile CLISP CVS HEAD on Debian 5 (lenny):
My cvs checkout directory from today's CVS HEAD is:
/home/edgar/Downloads/clisp/clisp-2010-09-25/...
The libsigsegv tarball is in:
/home/edgar/Downloads/clisp/libsigsegv-2.8.tar.gz
From the cvs-checkout directory I run this shell-script:
--- configure shell script ---
LIBSIGSEGV=libsigsegv-2.8
CONFIG_OPTS=--with-module=clx/new-clx
BUILD_DIR=linux-build
# make a "tools" directory inside the cvs checkout directory
mkdir tools
cd tools
# define "../cvs-checkout/tools/i686-pc-linux-gnu" as the libsigsegv prefix
# /home/edgar/Downloads/clisp/clisp-2010-09-25/tools/i686-pc-linux-gnu
prefix=$(pwd)/i686-pc-linux-gnu
# copy and unpack the libsigsegv tarball
cp ../../${LIBSIGSEGV}.tar.gz ./
tar xfz ${LIBSIGSEGV}.tar.gz
# in the libsigsegv directory, configure, make, and install libsigsegv
cd ${LIBSIGSEGV}/
./configure --prefix=${prefix} && make && make check && make install
# back to CLISP's cvs checkout directory
cd ../../
# configure CLISP
./configure --with-libsigsegv-prefix=${prefix} $CONFIG_OPTS $BUILD_DIR
# make sure we have enough stack space
ulimit -s 16384
--- end of configure shell script ---
At the end of ./configure CLISP tells me:
Configure findings:
FFI: yes (user requested: default)
readline: yes (user requested: default)
libsigsegv: yes
Then I go into the linux-build-directory:
cd linux-build
# edit the Lisp configuration
make
make check
sudo make install
libsigsegv found, all checks passed, CLISP works.
Please note that libsigsegv has been compiled with exactly the same
version of tools and libraries like CLISP (I sometimes in the past
had troble if this was not the case, but unfortunately can't tell
the exact reason why), and that libsigsegv had been installed in
"../cvs-checkout/tools/i686-pc-linux-gnu", as suggested in the CLISP
INSTALL docs. I haven't tested if the build fails if libsigsegv is
installed in "/usr/lib" or "/usr/local/lib".
More info about the machine and the tools if needed:
bash$ clisp --version
GNU CLISP 2.49+ (2010-07-17) (built 3494433303) (memory 3494434384)
Software: GNU-C 4.3.2
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type
-Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2
-fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI
-DDYNAMIC_MODULES -I. -lreadline -lncurses -ldl -lavcall -lcallback
-L/home/edgar/Downloads/clisp/clisp-2010-09-25/tools/i686-pc-linux-gnu/lib
-lsigsegv -lc libgnu_cl.a
SAFETY=0 HEAPCODES LINUX_NOEXEC_HEAPCODES GENERATIONAL_GC SPVW_BLOCKS
SPVW_MIXED TRIVIALMAP_MEMORY
libsigsegv 2.8
libreadline 5.2
Features:
(READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL
COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES
SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: /usr/local/lib/clisp-2.49+/
User language: ENGLISH
Machine: I686 (I686) compaq-evo..net [127.0.1.1]
bash$ uname -a
Linux compaq-evo 2.6.26-2-686 #1 SMP Mon Aug 30 07:01:57 UTC 2010 i686 GNU/Linux
bash$ cat /etc/issue
Debian GNU/Linux 5.0 \n \l
bash$ lsb_release -a
LSB Version: core-2.0-ia32:core-2.0-noarch:core-3.0-ia32:core-3.0-noarch:
core-3.1-ia32:core-3.1-noarch:core-3.2-ia32:core-3.2-noarch:cxx-3.0-ia32:
cxx-3.0-noarch:cxx-3.1-ia32:cxx-3.1-noarch:cxx-3.2-ia32:cxx-3.2-noarch:
desktop-3.1-ia32:desktop-3.1-noarch:desktop-3.2-ia32:desktop-3.2-noarch:
graphics-2.0-ia32:graphics-2.0-noarch:graphics-3.0-ia32:graphics-3.0-noarch:
graphics-3.1-ia32:graphics-3.1-noarch:graphics-3.2-ia32:graphics-3.2-noarch:
qt4-3.1-ia32:qt4-3.1-noarch
Distributor ID: Debian
Description: Debian GNU/Linux 5.0.6 (lenny)
Release: 5.0.6
Codename: lenny
Gnome Version: 2.22.3
- edgar
--
The author of this email does not necessarily endorse the following
advertisements, which are the sole responsibility of the advertiser:
|
|
From: Sam S. <sd...@gn...> - 2010-09-27 16:34:48
|
Vladimir Sedach wrote: > Tried building a CLISP I just pulled from CVS, on Debian 5. The installed > version of libsigsegv didn't work (older version), followed directions to build > and install libsigsegv-2.8, first with --prefix=/usr/local, then with --prefix=/ > usr (default), neither were detected by the ./configure script (passed --with- > libsigsegv-prefix parameter). I think the detection routine is in the > aclocal.m4 script, but not sure. Can someone double-check this? the detection routine is in src/glm4/libsigsegv.m4 which comes from gnulib. you should take a look at config.log for gcc error messages; if you cannot figure out the problem with your setup, you should complain to gnulib maintainers at <bug...@gn...>. |
|
From: Vladimir S. <vs...@gm...> - 2010-10-02 05:23:39
|
Turns out the key step I was missing was: rm src/config.cache Vladimir 2010/9/27 Sam Steingold <sd...@gn...>: > Vladimir Sedach wrote: >> >> Tried building a CLISP I just pulled from CVS, on Debian 5. The installed >> version of libsigsegv didn't work (older version), followed directions to >> build and install libsigsegv-2.8, first with --prefix=/usr/local, then with >> --prefix=/ >> usr (default), neither were detected by the ./configure script (passed >> --with- >> libsigsegv-prefix parameter). I think the detection routine is in the >> aclocal.m4 script, but not sure. Can someone double-check this? > > the detection routine is in src/glm4/libsigsegv.m4 which comes from gnulib. > you should take a look at config.log for gcc error messages; if you cannot > figure out the problem with your setup, you should complain to gnulib > maintainers at <bug...@gn...>. > |
|
From: Sam S. <sd...@gn...> - 2010-10-04 15:08:30
|
Vladimir Sedach wrote: > Turns out the key step I was missing was: > > rm src/config.cache it might be that what you actually need is "make distclean". this is why I recommend passing the build directory name to configure instead of building in src. then you can 'rm -rf' it. |
Thanks for helping keep SourceForge clean.
X