LinuxQuestions.org - SL14.0_x64:Installing Stumpwm: where is clisp-2.49/full/lisp.run ?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - SL14.0_x64:Installing Stumpwm: where is clisp-2.49/full/lisp.run ? (https://www.linuxquestions.org/questions/slackware-14/sl14-0_x64-installing-stumpwm-where-is-clisp-2-49-full-lisp-run-4175494375/)

SL14.0_x64:Installing Stumpwm: where is clisp-2.49/full/lisp.run ?

I am trying to compile the Stump Window Manager with clisp, but it fails:

Quote:

/usr/bin/clisp: /usr/lib64/clisp-2.49/full/lisp.run: No such file or directory

and it's right:

Quote:

# ls /usr/lib64/clisp-2.49/
base/ build-aux/ clx/ data/ dynmod/ linkkit/ pcre/ rawsock/ wildcard/ zlib/

I successfully compiled it on an earlier release. but now that I'm running 64bits, I have to recompile it.
However, I can't remember whether it was then compiled it with clisp or sbcl.

Does anyone understand this? Is it the same on 14.0_x32, sl14.1 etc?

I have checked the original slackbuild from source but I can't see a configuration option for "full".

Here is the listing of the compile:

Quote:

$ ./configure --with-lisp=clisp
checking for sbcl... no
checking for clisp... /usr/bin/clisp
checking for ccl... no
checking for ecl... no
configure: Using clisp at /usr/bin/clisp
checking for makeinfo... yes
checking for xdpyinfo... yes
checking for /path/to/stumpwm-0.9.7/cl-ppcre/cl-ppcre.asd... yes
configure: creating ./config.status
config.status: creating Makefile
configure: creating ./config.status
config.status: creating Makefile
config.status: creating make-image.lisp
configure: creating ./config.status
config.status: creating Makefile
config.status: creating make-image.lisp
config.status: creating version.lisp
configure: creating ./config.status
config.status: creating Makefile
config.status: creating make-image.lisp
config.status: creating version.lisp
config.status: creating module.lisp

$ make
/usr/bin/clisp -K full -on-error exit ./make-image.lisp
/usr/bin/clisp: /usr/lib64/clisp-2.49/full/lisp.run: No such file or directory
make: *** [stumpwm] Error 1

I'm not sure if this file is the same as the one the Makefile desires, but perhaps try editing the Makefile to point to this:

Code:

/usr/lib64/clisp-2.49/base/lisp.run

Instead of:

Code:

/usr/lib64/clisp-2.49/full/lisp.run

No, that doesn't seem to work. I was wondering whether clisp has been correctly installed - whether the standard slackware clisp install is some sort of subset of the clisp which stumpwm is expecting.

Quote:

/usr/bin/clisp -K base -on-error exit ./make-image.lisp
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/packages.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/packages.fas
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/specials.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/specials.fas
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/util.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/util.fas
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/errors.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/errors.fas
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/charset.lisp ...
WARNING: in IN-CHARSET-P in lines 87..126 : Unknown declaration CHARSET.
The whole declaration will be ignored.
WARNING: in %ADD-TO-CHARSET in lines 137..172 : Unknown declaration CHARSET.
The whole declaration will be ignored.
WARNING: in %ADD-TO-CHARSET/EXPAND in lines 174..210 : Unknown declaration CHARSET.
The whole declaration will be ignored.
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/charset.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL#x0003343B3B40> on #<CL-SOURCE-FILE
"charset" #x0003343AE088>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL#x0003343B3B40> on #<CL-SOURCE-FILE
"charset" #x0003343AE088>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/charmap.lisp ...
WARNING: in IN-CHARMAP-P in lines 52..65 : Unknown declaration CHARMAP.
The whole declaration will be ignored.
WARNING: in CHARMAP-CONTENTS in lines 67..76 : Unknown declaration CHARMAP.
The whole declaration will be ignored.
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/charmap.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL#x0003343B3B40> on #<CL-SOURCE-FILE
"charmap" #x0003343AE1D0>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"charmap" #x0003343AE1D0>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/chartest.lisp ...
WARNING: in CREATE-OPTIMIZED-TEST-FUNCTION-1 in lines 43..98 : Unknown declaration CHARMAP.
The whole declaration will be ignored.
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/chartest.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"chartest" #x0003343AE318>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"chartest" #x0003343AE318>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/lexer.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/lexer.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"lexer" #x0003343AE460>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"lexer" #x0003343AE460>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/parser.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/parser.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"parser" #x0003343AE5A8>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"parser" #x0003343AE5A8>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/regex-class.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/regex-class.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"regex-class" #x0003343AE6F0>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"regex-class" #x0003343AE6F0>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/regex-class-util.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/regex-class-util.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"regex-class-util" #x0003343AE838>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"regex-class-util" #x0003343AE838>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/convert.lisp ...
WARNING: in #:|323 329 (DEFGENERIC CONVERT-COMPOUND-PARSE-TREE (TOKEN PARSE-TREE &KEY) ...)-12-1-1|
in lines 323..329 : variable PARSE-TREE is not used.
Misspelled or missing IGNORE declaration?
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/convert.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"convert" #x0003343AE980>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"convert" #x0003343AE980>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/optimize.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/optimize.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"optimize" #x0003343AEAC8>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"optimize" #x0003343AEAC8>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/closures.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/closures.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"closures" #x0003343AEC10>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"closures" #x0003343AEC10>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/repetition-closures.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/repetition-closures.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"repetition-closures" #x0003343AED58>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343B3B40> on #<CL-SOURCE-FILE
"repetition-closures" #x0003343AED58>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/scanner.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/scanner.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343AF588> on #<CL-SOURCE-FILE
"scanner" #x0003343AA8E8>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343AF588> on #<CL-SOURCE-FILE
"scanner" #x0003343AA8E8>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/api.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/cl-ppcre/api.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343AF588> on #<CL-SOURCE-FILE
"api" #x0003343AAA30>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343AF588> on #<CL-SOURCE-FILE
"api" #x0003343AAA30>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/package.lisp ...
;; Wrote file /path/to/stumpwm/stumpwm-0.9.7/package.fas
WARNING: COMPILE-FILE warned while performing #<COMPILE-OP NIL #x0003343AEDA0> on #<CL-SOURCE-FILE
"package" #x0003343A5FB8>.
WARNING: COMPILE-FILE failed while performing #<COMPILE-OP NIL #x0003343AEDA0> on #<CL-SOURCE-FILE
"package" #x0003343A5FB8>.
;; Compiling file /path/to/stumpwm/stumpwm-0.9.7/primitives.lisp ...
*** - READ from
#<INPUT BUFFERED FILE-STREAM CHARACTER
#P"/path/to/stumpwm/stumpwm-0.9.7/primitives.lisp"
@609>
: there is no package with name "XLIB"

The following functions were used but not defined:
STUMPWM::RESTARTS-MENU STUMPWM::MESSAGE STUMPWM::DFORMAT
0 errors, 35 warnings
make: *** [stumpwm] Error 1

I think you have found a bug. Please report it to Pat.

Code:

dorkbutt@hp635:~$ clisp -K full

clisp: /usr/lib64/clisp-2.49/full/lisp.run: No such file or directory

flacy@hp635:~$

clisp -K base returns an interactive prompt; the clisp man page mentions that the full option should be supported that contains the

Quote:

core plus all the modules with which this installation was built, see Section 32.2, "External Modules".

I tried to build the version in git changing "-K full" with "-K base" in the Makefile.in before launching the ./configure: the error I got is

Code:

;; Loading file load-stumpwm.lisp ...

*** - LOAD: A file with name ASDF does not exist

Bye.

make: *** [stumpwm] Error 1

so I found this page in the archwiki: seems that if you want to build it with clisp you will need some additional modules (not tried here).

Quote:

Originally Posted by harryhaller (Post 5114641)

I successfully compiled it on an earlier release. but now that I'm running 64bits, I have to recompile it.
However, I can't remember whether it was then compiled it with clisp or sbcl.

judging from what I can read in the archwiki, I guess the latter.

Nonetheless, the clisp installation in Slackware64 14.1 is broken. "clisp -k full" should not return with an error message.

After playing around with the slackbuild and comparing it with the clisp unix build instructions, there are some steps omitted from the slackbuild that the unix build instructions say that you should do.

Of course, when I tried to perform the unix build instructions, I saw that the steps Pat omitted don't fricking work (i.e. build errors). Grr. I might have time to mess with it this weekend; we'll see.

I'm comparing the the builds between sl13.0 and sl14.0.

Although the slackbuilds are the same, the configuration scripts that came with clisp are different.

From comments made in the past here, it seems that clisp was ok for building stumpwm back in august 2010.

If the configuration file has changed, then the slackbuild should have changed as well - it didn't.

for example, this is new in the clisp-2.49 configuration file.

Quote:

all_modules=''
note_module(){
all_modules=${all_modules}" $1"
makemake_args=${makemake_args}" --with-module=$1"

The default for dynamic modules seems to have been reversed. I have no idea whatsoever whether these differences are significant or relevant. I'm right out of my depth here - I just wanted to build a WM :)

Well, the instructions for clisp tell you to eventually run the sequence...

Code:

        make init                prepares all symbolic links and utilities

        make allc                makes all *.c files

        make lisp.run            makes the executable runtime

          (cygwin & mingw: use "make lisp.exe" instead)

        make interpreted.mem    a memory image with everything uncompiled

        make halfcompiled.mem    a memory image with compiler.fas and

                                  the rest uncompiled

        make lispinit.mem        makes all *.fas files and

                                  a memory image with everything compiled

        make manual              makes the documentation

        make modular            prepares for module building

        make boot                makes the boot linking set (just the core)

        make base                makes the base linking set

                                  (boot + regexp + syscalls + i18n + readline)

        make full                makes the full linking set (base + your

                                  MODULES variable in Makefile, see step 5)

..but the slackbuild does...

Code:

make config.lisp

make init

make allc

make $NUMJOBS lisp.run

make interpreted.mem

make halfcompiled.mem

make lispinit.mem

make manual

make modular

.

In my quick tests, make boot finishes successfully but make base fails as well as make full.

OTOH, my make manual also blew up but that could be because I told it to ignore the missing libsigsegv.

As I said, I need to look at it closer.

Looks like an upstream error, but I can't find any reports of the problem or the fix.

Blech.

You'll need this patch...

Code:

--- src/makemake.in.orig        2014-02-17 01:40:48.077836493 -0600

+++ src/makemake.in        2014-02-17 01:41:27.529789829 -0600

@@ -1,4 +1,4 @@

-# -*- coding: utf-8; mode: shell-script -*- vim:filetype=sh

+/# -*- coding: utf-8; mode: shell-script -*- vim:filetype=sh

 # Creation of the Makefile used for compiling CLISP

 # Bruno Haible 1991-2008

 # Sam Steingold 1999-2010

@@ -3581,6 +3581,7 @@

    echotab "mkdir -p \$(DESTDIR)\$(lisplibdir)/linkkit"

    echotab "(cd \$(DESTDIR)\$(lisplibdir) && \$(RMRF) base full)"

    echotab "mkdir -p \$(DESTDIR)\$(lisplibdir)/base"

+    echotab "mkdir -p \$(DESTDIR)\$(lisplibdir)/full"

    echotab "mkdir -p \$(DESTDIR)\$(lisplibdir)/build-aux"

    echotab "for f in ${BUILD_AUX}; do \$(INSTALL_DATA) build-aux/\$\$f \$(DESTDIR)\$(lisplibdir)/build-aux/\$\$f; done"

    if [ "${with_dynamic_modules}" != no ]; then

@@ -3593,7 +3594,7 @@

      echotab "    mkdir -p \"\$\$absdest/\$\$m\"; \\"

      echotab "    cd \$\$m; \$(MAKE) clisp-module-distrib LN=\"\$(INSTALL_DATA)\" distribdir=\"\$\$absdest/\$\$m\" ; cd \"\$\$here\"; \\"

      echotab "  done; fi"

-      line='linkkit/* base/*'

+      line='linkkit/* base/* full/*'

    else

      echotab "mkdir -p \$(DESTDIR)\$(lisplibdir)/full"

      line='linkkit/* base/* full/*'

as well as changing the slackbuild from

Code:

cd with-gcc-wall

./makemake \

  --with-dynamic-ffi  \

  --prefix=/usr \

  --libdir=/usr/lib${LIBDIRSUFFIX} \

  --with-module=clx/new-clx \

  --with-module=pcre \

  --with-module=rawsock \

  --with-module=wildcard \

  --with-module=zlib \

  --srcdir=../src \

  > Makefile

make config.lisp

make init

make allc

make $NUMJOBS lisp.run

make interpreted.mem

make halfcompiled.mem

make lispinit.mem

make manual

make modular

Code:

cd with-gcc-wall



make -j1 init

make -j1 allc

make -j1 lisp.run

make -j1 interpreted.mem

make -j1 halfcompiled.mem

make -j1 lispinit.mem

make -j1 manual

make -j1 modular

make -j1 boot

make -j1 base

make -j1 full

since the build for this version won't build in parallel.

For my testing, I installed libsigsegv from Slackbuilds and used src2pkg to build and install ffcall-1.10 independently from the clisp installation. You don't have to do that. I didn't test stumpwm but it appeared to build, without fatal errors.