Aidan Gauland | 2 Jul 03:20 2011
Picon

[STUMP] Building with CLISP

I think StumpWM's build system needs to be updated to work with CLISP
2.49.  I tried building it on my Debian squeeze (stable) system (with
the CLISP package from wheezy (testing), because 2.49 is not in
squeeze), and got an error.  Here is my shell session from trying to
build.

Regards,
Aidan Gauland

$ git clone --depth 1 git://git.savannah.nongnu.org/stumpwm.git
Cloning into stumpwm...
remote: Counting objects: 401, done.
remote: Compressing objects: 100% (270/270), done.
remote: Total 401 (delta 270), reused 205 (delta 127)
Receiving objects: 100% (401/401), 444.36 KiB | 94 KiB/s, done.
Resolving deltas: 100% (270/270), done.
$ cd stumpwm/
$ autoconf
$ ./configure --with-lisp=clisp --with-ppcre=/usr/share/common-lisp/source/cl-ppcre
checking for sbcl... /usr/bin/sbcl
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 /usr/share/common-lisp/source/cl-ppcre/cl-ppcre.asd... yes
configure: creating ./config.status
config.status: creating Makefile
configure: creating ./config.status
(Continue reading)

Wang Lei | 3 Jul 01:52 2011
Picon

Re: [STUMP] Building with CLISP


On 2011-07-02 09:20:49 +0800, Aidan Gauland wrote:
> I think StumpWM's build system needs to be updated to work with CLISP
> 2.49.  I tried building it on my Debian squeeze (stable) system (with
> the CLISP package from wheezy (testing), because 2.49 is not in
> squeeze), and got an error.  Here is my shell session from trying to
> build.
>
> Regards,
> Aidan Gauland
>
> $ git clone --depth 1 git://git.savannah.nongnu.org/stumpwm.git
> Cloning into stumpwm...
> remote: Counting objects: 401, done.
> remote: Compressing objects: 100% (270/270), done.
> remote: Total 401 (delta 270), reused 205 (delta 127)
> Receiving objects: 100% (401/401), 444.36 KiB | 94 KiB/s, done.
> Resolving deltas: 100% (270/270), done.
> $ cd stumpwm/
> $ autoconf
> $ ./configure --with-lisp=clisp --with-ppcre=/usr/share/common-lisp/source/cl-ppcre
> checking for sbcl... /usr/bin/sbcl
> 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 /usr/share/common-lisp/source/cl-ppcre/cl-ppcre.asd... yes
> configure: creating ./config.status
(Continue reading)

Aidan Gauland | 3 Jul 03:43 2011
Picon

Re: [STUMP] Building with CLISP

Wang Lei <f3d27b <at> gmail.com> writes:

> On 2011-07-02 09:20:49 +0800, Aidan Gauland wrote:
>> $ make
>> /usr/bin/clisp -K full -on-error exit ./make-image.lisp
>> /usr/bin/clisp: /usr/lib/clisp-2.49/full/lisp.run: No such file or directory
>
> I have met this problem. Check if lisp.run is there. In my system, it's
> under directory
>
> /usr/lib/clisp-2.49/base
>
> . You can symlink it to /usr/lib/clisp-2.49/full.

On my system, there is no directory (or file) /usr/lib/clisp-2.49/full,
so I had to create it.  I then symlinked
/usr/lib/clisp-2.49/base/lisp.run to /usr/lib/clisp-2.49/full/ and ran
make.  Different error and still no joy.

$ make
/usr/bin/clisp -K full -on-error exit ./make-image.lisp
/usr/lib/clisp-2.49/full/lisp.run: operating system error during load of initialization file `/usr/lib/clisp-2.49/full/lispinit.mem'
[/build/clisp-QkfhfL/clisp-2.49/src/spvw_memfile.d:982] errno = ENOENT: No such file or directory.
make: *** [stumpwm] Error 1
$

--Aidan
Picon

[STUMP] run-shell-command - displaying message on program error

Current behaviour of run-shell-command when passing path to
non-existent program as argument to it is to do nothing, just silently
ignore error.
I've created a new command run-shell-command-display-errors which
displays error when passed argument program exits with non-zero
status. This behaviour is similar to Ion window manager run command
behaviour.
Here is some example stumpish session that show how commands differ.

> run-shell-command test
> run-shell-command-display-errors test
Program exited with code 1 and has
 error output
< empty >
 normal output
< empty >
> run-shell-command cat non-existent-file
> run-shell-command-display-errors cat non-existent-file
Program exited with code 1 and has
 error output
cat: non-existent-file: No such file or directory
 normal output
< empty >
>

Now in my config I replaced run-shell-command with
run-shell-command-display-errors

(define-key *root-map* (kbd "!") "run-shell-command-display-errors")

(Continue reading)

Dirk Sondermann | 3 Jul 14:58 2011
Picon

Re: [STUMP] Building with CLISP

On 07/02/11 03:20, Aidan Gauland wrote:
> I think StumpWM's build system needs to be updated to work with CLISP
> 2.49.  I tried building it on my Debian squeeze (stable) system (with
> the CLISP package from wheezy (testing), because 2.49 is not in
> squeeze), and got an error.  Here is my shell session from trying to
> build.
> ...
> $ make
> /usr/bin/clisp -K full -on-error exit ./make-image.lisp
> /usr/bin/clisp: /usr/lib/clisp-2.49/full/lisp.run: No such file or directory
> make: *** [stumpwm] Error 1

Debian builds clisp-2.49 with dynamic modules support, which has
become the default in that version. clx and other additional modules
are provided by separate packages now and there is no longer a "full"
linking set which contains all additional modules. But you can easily
create such a linking set by installing the desired clisp-module-*
packages and using clisp-link.

stumpwm needs the module new-clx (provided by clisp-module-clx), so
an appropriate "full" linking set may be created by

  clisp-link add /usr/lib/clisp-2.49/base \
                 /usr/lib/clisp-2.49/full \
                 /usr/lib/clisp-2.49/clx/new-clx

(Disclaimer: Since I'm not using Debian I did not test this procedure
with Debian's clisp. But it works with a clisp built from source.)

--
(Continue reading)

Dirk Sondermann | 4 Jul 00:10 2011
Picon

Re: [STUMP] Building with CLISP

On 07/03/11 14:58, Dirk Sondermann wrote:
> But you can easily create such a linking set by installing the
> desired clisp-module-* packages and using clisp-link.

As a more convenient alternative, you may apply the patch posted by
Ben Spencer on March 22 on this list. Since make-image.lisp.in has
changed in the meantime, I've attached an updated version of that
patch.

--
Dirk
_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
Wojciech Meyer | 4 Jul 00:46 2011

Re: [STUMP] [PATCH] Initial interface to pwsafe password keyring. Two new commands: `pwsafe-menu', `pwsafe-entry'.

Ping ;) Please see the patch in my previous e-mails.

Wojciech

Wojciech Meyer <wojciech.meyer <at> googlemail.com> writes:

> Hi,
>
> Could anybody review the patch please, I wish this contribution will end
> up eventually in Stump. As a sort of encouragement I have more ideas and
> patches to go soon. I did my best for you to spend as minimal time as
> it's needed on reviewing it.
>
> TIA
> Wojciech
>
> Wojciech Meyer <wojciech.meyer <at> googlemail.com> writes:
>
>> Ping ;)
>>
>> Wojciech Meyer <wojciech.meyer <at> googlemail.com> writes:
>>
>>> Hi Guys,
>>>
>>> Since I've been using pwsafe quite often, and I've never felt
>>> comfortable with using available gui interfaces, Emacs mode has never
>>> worked for me, and more importantly now there is a way of handling
>>> passwords in StumpWM, I've been yield to temptation to write an
>>> interface for StumpWM to handle basic pwsafe work-flow - selecting
>>> account and getting password and the user name.
(Continue reading)

Ben Spencer | 4 Jul 08:23 2011
Picon

Re: [STUMP] Building with CLISP

On Mon, Jul 04, 2011 at 12:10:19AM +0200, Dirk Sondermann wrote:
> As a more convenient alternative, you may apply the patch posted by
> Ben Spencer on March 22 on this list. Since make-image.lisp.in has
> changed in the meantime, I've attached an updated version of that
> patch.

Unfortunately this makes it build but the resulting binary doesn't work:

ben <at> arctor:~/src/stumpwm$ ./stumpwm
module 'syscalls' requires package OS.

I guess it needs to be told to load the required modules on startup.
Any ideas?

Ben
Dirk Sondermann | 5 Jul 00:56 2011
Picon

Re: [STUMP] Building with CLISP

On 07/04/11 08:23, Ben Spencer wrote:
> On Mon, Jul 04, 2011 at 12:10:19AM +0200, Dirk Sondermann wrote:
>> As a more convenient alternative, you may apply the patch posted by
>> Ben Spencer on March 22 on this list. Since make-image.lisp.in has
>> changed in the meantime, I've attached an updated version of that
>> patch.
> 
> Unfortunately this makes it build but the resulting binary doesn't work:
> 
> ben <at> arctor:~/src/stumpwm$ ./stumpwm
> module 'syscalls' requires package OS.
> 
> I guess it needs to be told to load the required modules on startup.
> Any ideas?

No. It seems that saved images fail to start as soon as dynamic modules
are involved (even in the simplest case):

$ clisp -x '(require "clx")' -x '(ext:saveinitmem "test" :executable t)'
$ ./test
module 'syscalls' requires package OS.

This problem has been solved in the clisp version from the Mercurial
repository:

$ ./test
...
Welcome to GNU CLISP 2.49+
...
[1]> (xlib:window-p nil)
(Continue reading)

Dirk Sondermann | 7 Jul 01:46 2011
Picon

Re: [STUMP] Building with CLISP

On 07/04/11 08:23, Ben Spencer wrote:
> On Mon, Jul 04, 2011 at 12:10:19AM +0200, Dirk Sondermann wrote:
>> As a more convenient alternative, you may apply the patch posted by
>> Ben Spencer on March 22 on this list. Since make-image.lisp.in has
>> changed in the meantime, I've attached an updated version of that
>> patch.
> 
> Unfortunately this makes it build but the resulting binary doesn't work:
> 
> ben <at> arctor:~/src/stumpwm$ ./stumpwm
> module 'syscalls' requires package OS.

I've combined your patch with the creation of a temporary linking
set using clisp-link. The resulting binary now actually works.

For building stumpwm on Debian wheezy with this patch, in addition
to the packages clisp and clisp-module-clx also clisp-dev has to
be installed.

--
Dirk

_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
(Continue reading)


Gmane