ort will ever be saved by
upgrading CLISP and checking that the existing image is compatible with
the new CLISP. It is safer and cleaner to _always_ re-dump the MEM file
from FAS.gz distributed with the package.
I think this is what Bruno meant by his ls.so analogy.
Thanks.
--
Sam Steingold (
this is not debian-related.
this is an upstream bug
https://sourceforge.net/tracker/index.php?func=detail&aid=2014262&group_id=1355&atid=101355
which has now been fixed in the CVS.
it will be available in clisp 2.47
in the future, please report such bugs directly to us using the SF bug
tracker.
th
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=2015118&group_id=1355
the bug is now fixed: an arithmetic-error is signaled instead of a stack
overflow.
2.47 will include this fix.
___
pkg-common-lisp-devel mailing list
pkg-common-lisp-
this bug has been fixed in clisp cvs head and will be available in 2.47.
___
pkg-common-lisp-devel mailing list
pkg-common-lisp-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel
Luca Capello wrote:
> On Fri, 11 Jul 2008 00:01:10 +0200, Sam Steingold wrote:
>> this bug has been fixed in clisp cvs head and will be available in
>> 2.47.
>
> Thank you Sam! For information's sake, I guess this is reflected by the
> following ChangeLog
I cannot try this because I do not have ordrules.h, but I don't see how
this can happen: the line
register_foreign_inttype("tcflag_t",sizeof(tcflag_t),(tcflag_t)-1<=(tcflag_t)0);
is generated by
(def-c-type tcflag_t)
and there is no such line in the lisp file you attach.
please file a clisp b
src/makemake.in detects mips64, so it creates arimips64.c (as is clear
from your log) not arimips.c.
please try to run in full 64-bit mode or full 32-bit mode.
___
pkg-common-lisp-devel mailing list
pkg-common-lisp-devel@lists.alioth.debian.org
http:/
$ grep X_PRE_ config.log
X_PRE_LIBS=' -lSM -lICE'
X_PRE_LIBS is set by the standard autoconf macro AC_PATH_XTRA,
invoked by modules/clx/new-clx/configure
if you want, you can try to replace AC_PATH_XTRA with AC_PATH_X,
regenerate configures &c and see if it still works.
_
> * Luca Capello <[EMAIL PROTECTED]> [2008-07-20 21:48:29 +0200]:
>
> On Tue, 15 Jul 2008 15:54:13 +0200, Sam Steingold wrote:
>> $ grep X_PRE_ config.log
>> X_PRE_LIBS=' -lSM -lICE'
>>
>> X_PRE_LIBS is set by the standard autoconf macro AC_PATH_
Hi,
now that clisp 2.47 has been released, you are 3 releases behind. :-)
A couple notes about the debian package:
1. README.Debian says "In order to use the "disassemble" function you must
install gdb". this is NOT true. gdb is only necessary to disassemble functions
written in C, e.g., car. f
Package: clisp-dev
Version: 1:2.44.1-4.1
http://packages.debian.org/sid/clisp-dev
lists far too many dependencies.
clisp-dev does not require a specific gcc version.
all it needs is some C compiler, not necessarily the one which was used to
build clisp
there is absolutely no need for bison, deb
> BTW, I read the pkg-common-lisp mailing list on a regular basis, so you
> do not need to cc: me.
I don't think my mails there are accepted.
(do I have to be subscribed? if yes, can I disable delivery and read it on
gmane?)
> On Fri, 24 Oct 2008 21:50:39 +0200, Sam Steingold wrot
y planned to solve this issue splitting
>the Debian clisp package into clisp-base and clisp-full, but I have
>not had time yet :-(
>
> 2) makevars wants to include all of the libraries listed in clisp-dev
>Depends:, that is why these libraries are, in the Debian world,
>
ea for debian to
follow those suggestions.
I am mostly concerned with "offering a uniform experience to all CLISP
users regardless of platform or distribution".
>>> Footnotes:
>>> [4] http://bugs.debian.org/177057
>>> [5] http://bugs.debian.org/462085
--
Hi Luca,
Luca Capello wrote:
> On Sun, 23 Nov 2008 21:09:15 +0100, Sam Steingold wrote:
>
>> you might also build clisp with dynamic modules and offer individual
>> modules a la carte.
>
> While my previous point is still valid, thank you for the hint: I have
> neve
Package: libsigsegv-dev
Version: 2.5-2
on dual-arch systems, specifically, on sparc (but possibly others),
libsigsegv.so is distributed in a 32-bit variant, not 64-bit variant:
/usr/lib/libsigsegv.so.0.0.0: ELF 32-bit MSB shared object, SPARC32PLUS, V8+
Required, version 1 (SYSV), dynamically li
see also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511024
--
Sam Steingold
___
pkg-common-lisp-devel mailing list
pkg-common-lisp-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel
move "full" (b) place directory "modname/" and files
"dynmod/*modname*" into the "clisp-modname" package (c) place the rest
into the "clisp" package.
Alternatively, pass '--with-module=rawsock --with-module=... ....' to
the top-level configu
OK, I fixed clisp-link.in and makemake.in (get them from CVS).
The relevant part of unix/INSTALL now reads:
==
3. Binary package creation: we recommend distributing module "clisp" containing
just the base linking set and individual modules packaged sep
1:2.49-1
> Source: clisp
> Source-Version: 1:2.49-1
--
Sam Steingold <http://sds.podval.org>
___
pkg-common-lisp-devel mailing list
pkg-common-lisp-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel
20 matches
Mail list logo
