gmane.lisp.clisp.devel

Re: Test failure on ARM

Jerry James — 2012-05-25T20:39:09

I don't know what the right fix for this is.  Just to get the build
going again, I took the dumb but simple approach:

--- src/makemake.in.orig2012-05-24 09:42:10.000000000 -0600
+++ src/makemake.in2012-05-24 17:28:54.160000792 -0600
< at >< at > -1130,6 +1130,10 < at >< at >
     * ) cpu=${host_cpu}
   esac
 fi
+# Kludge to get the arm build going again
+if test "$cpu" = armel; then
+  cpu=arm
+fi

 test "${verbose}" = true -o "${verbose}" = yes && \
   cat <<EOF >&2

I kicked off another build with mercurial tip this morning.  It just failed:

boot/lisp.run -B . -M boot/lispinit.mem -norc -q -i i18n/preload.lisp
-i syscalls/preload.lisp -i regexp/preload.lisp -x (saveinitmem
"base/lispinit.mem")
;; Loading file i18n/preload.lisp ...
;; Loaded file i18n/preload.lisp
;; Loading file syscalls/preload.lisp ...
;; Loaded file syscalls/preload.lisp
;; Loading file regexp/preload.lisp ...
;; Loaded file regexp/preload.lisp
*** - handle_fault error2 ! address = 0x36bcd0f4 not in
[0x1abf0000,0x1ad3bf28) !
SIGSEGV cannot be cured. F

Re: [ clisp-Patches-3529615 ] ARM fixes

Sam Steingold — 2012-05-25T01:41:43

Bruno,


do we need to support v4?

[ clisp-Patches-3529607 ] Format specifier patch

SourceForge.net — 2012-05-25T01:37:08

Patches item #3529607, was opened at 2012-05-24 15:52
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=301355&aid=3529607&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jerry James (jjames)
Assigned to: Nobody/Anonymous (nobody)
Summary: Format specifier patch

Initial Comment:
While compiling on a 32-bit platform, I saw some GCC warnings about printf arguments not matching the corresponding format specifiers.  This patch fixes all of the warnings I saw on that platform.

----------------------------------------------------------------------

Date: 2012-05-24 18:37

Message:
this patch results in these warnings on amd64:

In file included from ../src/spvw.d:161:0:
../src/spvw_debug.d: In function

Re: Test failure on ARM

Jerry James — 2012-05-24T23:24:03

I just posted a patch for this problem on sourceforge.  Now the build
goes a lot farther, but ultimately crashes.  The crash is identical to
one that was earlier identified as being related to generational
garbage collection.  So I turned off generational GC and tried again,
only to have the build crash with a different segfault, which has also
been connected to garbage collection.

Maybe these problems have been fixed since the 2.49 release.  I tried
building with mercurial head, only to have a different build failure
because host_cpu_c_abi is set to "armel" instead of "arm" in makemake,
resulting in all of the ARM-specific code being skipped.  That's all
the time I have to mess with it today.  I'll try to patch that up
tomorrow.

[ clisp-Patches-3529615 ] ARM fixes

SourceForge.net — 2012-05-24T23:02:27

Patches item #3529615, was opened at 2012-05-24 16:02
Message generated for change (Tracker Item Submitted) made by jjames
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=301355&aid=3529615&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jerry James (jjames)
Assigned to: Nobody/Anonymous (nobody)
Summary: ARM fixes

Initial Comment:
As reported recently on the mailing list, I have had some problems with clisp failing to build on ARM platforms.  WIth the help of Google and the ARM assembly language reference manual, I think I have all the problems sorted out now.  The illegal instruction problem I reported is due to lines like this:

LDMFD sp!, {v1,v2,v3,v4,v5,v6,pc}^

The trailing carat indicates that this is a return-from-exception.  But it isn't.  All i

[ clisp-Patches-3529607 ] Format specifier patch

SourceForge.net — 2012-05-24T22:52:20

Patches item #3529607, was opened at 2012-05-24 15:52
Message generated for change (Tracker Item Submitted) made by jjames
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=301355&aid=3529607&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jerry James (jjames)
Assigned to: Nobody/Anonymous (nobody)
Summary: Format specifier patch

Initial Comment:
While compiling on a 32-bit platform, I saw some GCC warnings about printf arguments not matching the corresponding format specifiers.  This patch fixes all of the warnings I saw on that platform.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=301355&aid=3529607&group_id=1355

---------------------------------

Re: Test failure on ARM

Jerry James — 2012-05-18T21:28:24

Thanks, Sam.  I'm going to make one more attempt before I file a bug.
I'm going to try building the latest mercurial sources and see if the
same problem occurs.  We're stilling distributing vanilla 2.49 in
Fedora.  Should we be?

Anyway, compiling on the ARM VM takes a very long time, so I probably
won't have time to get to it until Monday or Tuesday.  If it suffers
the same failure, I'll file a bug.  If not, I'll see if I can figure
out what commit fixes the problem.

Regards,

Re: Test failure on ARM

Sam Steingold — 2012-05-18T20:05:47

I cannot help with the specific problem, but I will ask you to file a
CLISP bug report on SF.

You can disable all assembly by adding -DNO_ASM to CFLAGS (either at
configure time as "./configure CFLAGS=-DNO_ASM build-no-asm" or by editing
the Makefile and doing "make clean"). Please see clisp/unix/PLATFORMS
for more information.

Re: Test failure on ARM

Jerry James — 2012-05-18T17:39:39

I finally got around to figuring out how to create an ARM VM with
qemu.  I've got the upcoming Fedora 17 release running on that VM.
The problem is not in ffcall after all.  The illegal instruction error
is occurring on the very last instruction of copy_loop_up_l2() in
src/ariarm.d.  A disassembly with GDB shows:

0x00106b3c <+0>:     ldm     r0!, {r2, r4, r12, lr}
0x00106b40 <+4>:     stmia   r1!, {r2, r4, r12, lr}
0x00106b44 <+8>:     subs    r3, r3, #8
0x00106b48 <+12>:    ldmge   r0!, {r2, r4, r12, lr}
0x00106b4c <+16>:    stmiage r1!, {r2, r4, r12, lr}
0x00106b50 <+20>:    bgt     0x106b3c <copy_loop_up_l2>
0x00106b54 <+24>:    mov     r0, r1
0x00106b58 <+28>:    ldm     sp!, {r4, pc}^

It's that last ldm instruction, at +28, that is the problem.  Also, I
see this from compilation of src/ariarm.s:
ariarm.s: Assembler messages:
ariarm.s:1: Warning: ignoring attempt to redefine built-in register 'a1'
ariarm.s:2: Warning: ignoring attempt to redefine built-in register 'a2'
ariarm.s:3: Warning: ignoring at

[ clisp-Bugs-3525509 ] CLISP treats CL:REQUIRE specially at compiletime

SourceForge.net — 2012-05-10T12:51:54

Bugs item #3525509, was opened at 2012-05-10 05:48
Message generated for change (Comment added) made by xach
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3525509&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: lisp error
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Zach Beane (xach)
Assigned to: Bruno Haible (haible)
Summary: CLISP treats CL:REQUIRE specially at compile time

Initial Comment:
I have a file "test.lisp" that contains only this:

  (require 'bogus)

When I start "clisp -ansi -norc" and issue (compile-file "test.lisp"), I get this:

    [1]> (compile-file "test.lisp")
    ;; Compiling file /home/xach/test.lisp ...
    *** - LOAD: A file with name BOGUS does not exist
    The following restarts are available:
    ABORT          :R1      Abort main loop
    Break 1 [2]> :bt

[ clisp-Bugs-3525509 ] CLISP treats CL:REQUIRE specially at compiletime

SourceForge.net — 2012-05-10T12:48:32

Bugs item #3525509, was opened at 2012-05-10 05:48
Message generated for change (Tracker Item Submitted) made by xach
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3525509&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: lisp error
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Zach Beane (xach)
Assigned to: Bruno Haible (haible)
Summary: CLISP treats CL:REQUIRE specially at compile time

Initial Comment:
I have a file "test.lisp" that contains only this:

  (require 'bogus)

When I start "clisp -ansi -norc" and issue (compile-file "test.lisp"), I get this:

    [1]> (compile-file "test.lisp")
    ;; Compiling file /home/xach/test.lisp ...
    *** - LOAD: A file with name BOGUS does not exist
    The following restarts are available:
    ABORT          :R1      Abort main loop
    Break 1 [2]>

[ clisp-Bugs-3524255 ] ANSI CL forbids mixed-type complex numbers

SourceForge.net — 2012-05-07T14:40:14

Bugs item #3524255, was opened at 2012-05-06 22:38
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3524255&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: ANSI compliance issue
Resolution: Invalid
Priority: 5
Private: No
Submitted By: John Cowan (johnwcowan)
Assigned to: Bruno Haible (haible)
Summary: ANSI CL forbids mixed-type complex numbers

Initial Comment:
CLHS (under Function COMPLEX) says that the real and imaginary parts of a complex numbers must either be both rational or both of the same float type, and if they are not, floating-point coercion must be done.  One of the given examples is (complex 1 .99) =>  #C(1.0 0.99).

But in CLISP, (integerp (realpart (complex 1 .99)) => #t.  This means that the real part is being stored as a rational number, sin

[ clisp-Bugs-3524255 ] ANSI CL forbids mixed-type complex numbers

SourceForge.net — 2012-05-07T14:11:02

Bugs item #3524255, was opened at 2012-05-06 22:38
Message generated for change (Comment added) made by johnwcowan
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3524255&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: ANSI compliance issue
Resolution: Invalid
Priority: 5
Private: No
Submitted By: John Cowan (johnwcowan)
Assigned to: Bruno Haible (haible)
Summary: ANSI CL forbids mixed-type complex numbers

Initial Comment:
CLHS (under Function COMPLEX) says that the real and imaginary parts of a complex numbers must either be both rational or both of the same float type, and if they are not, floating-point coercion must be done.  One of the given examples is (complex 1 .99) =>  #C(1.0 0.99).

But in CLISP, (integerp (realpart (complex 1 .99)) => #t.  This means that the real part is being stored as a rational numb

[ clisp-Bugs-3524255 ] ANSI CL forbids mixed-type complex numbers

SourceForge.net — 2012-05-07T13:51:50

Bugs item #3524255, was opened at 2012-05-06 22:38
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3524255&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: ANSI compliance issue
Priority: 5
Private: No
Submitted By: John Cowan (johnwcowan)
Assigned to: Bruno Haible (haible)
Summary: ANSI CL forbids mixed-type complex numbers

Initial Comment:
CLHS (under Function COMPLEX) says that the real and imaginary parts of a complex numbers must either be both rational or both of the same float type, and if they are not, floating-point coercion must be done.  One of the given examples is (complex 1 .99) =>  #C(1.0 0.99).

But in CLISP, (integerp (realpart (complex 1 .99)) => #t.  This means that the real part is being stored as a rational number, since there is no coerc

[ clisp-Bugs-3524255 ] ANSI CL forbids mixed-type complex numbers

SourceForge.net — 2012-05-07T05:38:38

Bugs item #3524255, was opened at 2012-05-06 22:38
Message generated for change (Tracker Item Submitted) made by johnwcowan
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3524255&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: ANSI compliance issue
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: John Cowan (johnwcowan)
Assigned to: Bruno Haible (haible)
Summary: ANSI CL forbids mixed-type complex numbers

Initial Comment:
CLHS (under Function COMPLEX) says that the real and imaginary parts of a complex numbers must either be both rational or both of the same float type, and if they are not, floating-point coercion must be done.  One of the given examples is (complex 1 .99) =>  #C(1.0 0.99).

But in CLISP, (integerp (realpart (complex 1 .99)) => #t.  This means that the real part is being stored

clisp-cvs Digest, Vol 70, Issue 1

2012-05-04T12:05:07

Send clisp-cvs mailing list submissions to
clisp-cvs< at >lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/clisp-cvs
or, via email, send a message with subject or body 'help' to
clisp-cvs-request< at >lists.sourceforge.net

You can reach the person managing the list at
clisp-cvs-owner< at >lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of clisp-cvs digest..."


CLISP CVS commits for today

Today's Topics:

   1. clisp: update berkeley-db to 5.1
      (clisp-cvs-request< at >lists.sourceforge.net)


----------------------------------------------------------------------

Message: 1
Date: Fri, 04 May 2012 05:04:37 +0000
From: clisp-cvs-request< at >lists.sourceforge.net
Subject: clisp: update berkeley-db to 5.1
To: clisp-cvs< at >lists.sourceforge.net
Message-ID:
<hg.3d1765c46a62.1336107877.-3352671374714820773< at >vz-hg-2.sog>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.so

clisp-cvs Digest, Vol 69, Issue 6

2012-04-28T12:05:01

Send clisp-cvs mailing list submissions to
clisp-cvs< at >lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/clisp-cvs
or, via email, send a message with subject or body 'help' to
clisp-cvs-request< at >lists.sourceforge.net

You can reach the person managing the list at
clisp-cvs-owner< at >lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of clisp-cvs digest..."


CLISP CVS commits for today

Today's Topics:

   1. clisp: Fix bug#3467762: symlink to directory handling
      (clisp-cvs-request< at >lists.sourceforge.net)


----------------------------------------------------------------------

Message: 1
Date: Fri, 27 Apr 2012 19:29:03 +0000
From: clisp-cvs-request< at >lists.sourceforge.net
Subject: clisp: Fix bug#3467762: symlink to directory handling
To: clisp-cvs< at >lists.sourceforge.net
Message-ID:
<hg.c88260c2da71.1335554943.-3352671374714820773< at >vz-hg-3.sog>
Content-Type: text/plain; charset

[ clisp-Bugs-3521402 ] ffcall-1.10 (or CVS head) fails to buildx86_64 on OS X

SourceForge.net — 2012-04-27T22:10:55

Bugs item #3521402, was opened at 2012-04-25 11:26
Message generated for change (Settings changed) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3521402&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: ffcall
Group: build problems
Priority: 5
Private: No
Submitted By: Hanspeter Niederstrasser (nieder)
Assigned to: Bruno Haible (haible)
Summary: ffcall-1.10 (or CVS head) fails to build x86_64 on OS X

Initial Comment:
On OS X 10.6 (and 10.7) which builds as 64bit by default, ffcall fails to build with the following error:

./configure --host=x86_64-apple-darwin10 (explicit --host is needed or it misidentifies as a 32 bit and that also fails in a 64bit environment [1] )
...
cd avcall; make all
/bin/sh ./libtool --mode=compile gcc -x none -c ./avcall-x86_64.s
gcc -x none -c ./avcall-x86_64.s -o avcall-x86_64.o
avcall-

[ clisp-Bugs-3521402 ] ffcall-1.10 (or CVS head) fails to buildx86_64 on OS X

SourceForge.net — 2012-04-27T21:03:21

Bugs item #3521402, was opened at 2012-04-25 11:26
Message generated for change (Comment added) made by nieder
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3521402&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: ffcall
Group: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hanspeter Niederstrasser (nieder)
Assigned to: Bruno Haible (haible)
Summary: ffcall-1.10 (or CVS head) fails to build x86_64 on OS X

Initial Comment:
On OS X 10.6 (and 10.7) which builds as 64bit by default, ffcall fails to build with the following error:

./configure --host=x86_64-apple-darwin10 (explicit --host is needed or it misidentifies as a 32 bit and that also fails in a 64bit environment [1] )
...
cd avcall; make all
/bin/sh ./libtool --mode=compile gcc -x none -c ./avcall-x86_64.s
gcc -x none -c ./avcall-x86_6

[ clisp-Bugs-3467762 ] delete-file cannot delete directory symlink

SourceForge.net — 2012-04-27T19:30:59

Bugs item #3467762, was opened at 2011-12-30 18:52
Message generated for change (Settings changed) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3467762&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: lisp error
Priority: 5
Private: No
Submitted By: Gabor Balazs (gabalz)
Summary: delete-file cannot delete directory symlink

Initial Comment:

The delete-file function can remove file and dead symlinks but not (alive) directory symlinks, because it always resolves the provided pathname in the directory symlink case even if it should not (according to the CLISP documentation) :

    "(DELETE-FILE pathname) deletes the pathname PATHNAME, not its TRUENAME, ..."

Problem reconstruction:
~~~~~~~~~~~~~~~~~~

ls -lR
drwxr-xr-x 2 bege users 4096 Dec 30 19:40 dir
-rw-r--r-- 1 bege users    0 Dec 30 19:26 file
lrw

Re: A few newbie questions

Pascal J. Bourguignon — 2012-04-27T18:11:53


There's no variable named values.
There's a function named values, which returns a variable number of
values: one of each argument.

Therefore (values) returns no value, since it has no argument.


A function doesn't return nil by default, it returns whatever its
returning form returns.  In this case if you remove the call to VALUES,
it's FORMAT which returns only one value, nil, which are taken by the
implicit PROGN which returns them, which are taken by the BLOCK
<function-name> which returns them, which are taken by the LAMBDA
implicit PROGN which returns them.