clisp-devel — closed list for developers and testers

Re: make check failures

[Sam S. <sd...@gn...>]

Hi,

> * Dan Stanger <qna...@vr...> [2011-09-18 15:59:02 -0400]:
>
> I am building clisp with mingw in the directory mingw-build and I am 
> running into 2 problems with make check, and a third makemake problem.
> First, ext-clisp.tst fails with the following message:
> SYSTEM::SET-CURRENT-LANGUAGE: locales "en_US.utf8" and "en_US" are not 
> installed on this system.

I will let Bruno handle this.

> Should there be directories ex_US and ex_US.utf8 in the directory 
> mingw-build/locales created by the build process?
> Isn't that where set-current-language would look during the make-check 
> processing?
>
> Second, the socket test is hanging, requiring me to kill the spawned 
> lisp process to finish the tests.
> Following is the form:
>   (MULTIPLE-VALUE-BIND (RUN ARGS) (CMD-ARGS) (LET ((IS (RUN-PROGRAM RUN 
> :ARGUMENTS (APPEND ARGS '("-q" "-q" "-x" "
>              (let ((se (socket:socket-server)))
>                (write-line (princ-to-string (socket:socket-server-port se)))
>                (with-open-stream (so (socket:socket-accept se))
>                  (write-line (lisp-implementation-version) so))
>                (socket:socket-server-close se))")) :INPUT NIL :OUTPUT 
> :STREAM)))
> (LOOP :UNTIL (DIGIT-CHAR-P (PEEK-CHAR NIL IS)) :DO (READ-LINE IS)) 
> (WITH-OPEN-STREAM (SO (SOCKET-CONNECT (READ IS) "localhost" :TIMEOUT 
> 10)) (STRING= (LISP-IMPLEMENTATION-VERSION) (READ-LINE SO)))))

I have seen that, but I no longer have access to a windows system, so I
have an excuse for not fixing this.
This was introduced when gnulib pulled in a bunch of socket stuff like
rpl_socket (I complained to the gnulib people but to no avail), you can
either wait for Bruno to fix this of do it yourself.

> Third, the following targets are missing from the makefile on mingw, but 
> are present in cygwin:
> distmakefile
> install
> installdirs
> install-modules
> install-bin
> install-man
> install-doc
> installcheck
> uninstall
> uninstall-bin
> uninstall-man
>
> Has anyone else had any of these issues?

there is no "install" on a window system; there is "distrib" which you
then install.

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.04 (natty) X 11.0.11001000
http://www.memritv.org http://mideasttruth.com http://openvotingconsortium.org
http://pmw.org.il http://dhimmi.com http://palestinefacts.org http://memri.org
You do not have time or money to sue anyone rich enough to be worth suing.

make check failures

[Dan S. <dan...@ie...>]

Hello All,
I am building clisp with mingw in the directory mingw-build and I am 
running into 2 problems with make check, and a third makemake problem.
First, ext-clisp.tst fails with the following message:
SYSTEM::SET-CURRENT-LANGUAGE: locales "en_US.utf8" and "en_US" are not 
installed on this system.

Should there be directories ex_US and ex_US.utf8 in the directory 
mingw-build/locales created by the build process?
Isn't that where set-current-language would look during the make-check 
processing?

Second, the socket test is hanging, requiring me to kill the spawned 
lisp process to finish the tests.
Following is the form:
  (MULTIPLE-VALUE-BIND (RUN ARGS) (CMD-ARGS) (LET ((IS (RUN-PROGRAM RUN 
:ARGUMENTS (APPEND ARGS '("-q" "-q" "-x" "
             (let ((se (socket:socket-server)))
               (write-line (princ-to-string (socket:socket-server-port se)))
               (with-open-stream (so (socket:socket-accept se))
                 (write-line (lisp-implementation-version) so))
               (socket:socket-server-close se))")) :INPUT NIL :OUTPUT 
:STREAM)))
(LOOP :UNTIL (DIGIT-CHAR-P (PEEK-CHAR NIL IS)) :DO (READ-LINE IS)) 
(WITH-OPEN-STREAM (SO (SOCKET-CONNECT (READ IS) "localhost" :TIMEOUT 
10)) (STRING= (LISP-IMPLEMENTATION-VERSION) (READ-LINE SO)))))

Third, the following targets are missing from the makefile on mingw, but 
are present in cygwin:
distmakefile
install
installdirs
install-modules
install-bin
install-man
install-doc
installcheck
uninstall
uninstall-bin
uninstall-man

Has anyone else had any of these issues?
Thank you,
Dan Stanger

Re: Unable to get clisp to compile in MacPorts

[Sam S. <sd...@gn...>]

> * Yves S. Garret <lbh...@tz...> [2011-09-16 19:59:38 -0400]:
>
> gcc -I/Users/ysg/Downloads/CLisp/clisp/src/gllib -g -O2 -W -Wswitch
> -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations
> -Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4
> -DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES -DNO_GETTEXT
>  ../utils/comment5.c -o comment5
> In file included from /usr/include/sys/time.h:198,
>                  from
> /Users/ysg/Downloads/CLisp/clisp/src/gllib/sys/time.h:39,
>                  from
> /Users/ysg/Downloads/CLisp/clisp/src/gllib/sys/select.h:59,
>                  from /usr/include/unistd.h:672,
>                  from
> /Users/ysg/Downloads/CLisp/clisp/src/gllib/unistd.h:44,
>                  from
> /Users/ysg/Downloads/CLisp/clisp/src/gllib/stdlib.h:90,
>                  from ../utils/comment5.c:29:
> /Users/ysg/Downloads/CLisp/clisp/src/gllib/time.h:469: error: expected ‘;’,
> ‘,’ or ‘)’ before ‘__timer’
> /Users/ysg/Downloads/CLisp/clisp/src/gllib/time.h:491: error: expected ‘;’,
> ‘,’ or ‘)’ before ‘__timer’
> make: *** [comment5] Error 1

please report this to the gnulib maintainers (bug...@gn...)


-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.04 (natty) X 11.0.11001000
http://mideasttruth.com http://jihadwatch.org http://honestreporting.com
http://camera.org http://pmw.org.il http://iris.org.il
There are many reasons not to use Lisp - but no good ones.

clisp-cvs Digest, Vol 64, Issue 1

[<cli...@li...>]

Send clisp-cvs mailing list submissions to
	cli...@li...

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
	cli...@li...

You can reach the person managing the list at
	cli...@li...

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: * src/makemake.in (clean5): do not remove modules.h
      twice (cli...@li...)
   2. clisp: * modules/readline/readline.lisp: include rlconf.h for
      (cli...@li...)
   3. clisp: * src/m4/clisp.m4 (CL_DECOLONIZE): fix the 2011-07-25
      154... (cli...@li...)
   4. clisp: * src/pathname.d (assure_dir_exists): call
      merge-pathname... (cli...@li...)
   5. clisp: regenerate for decolonize/mingw 15548
      (cli...@li...)


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

Message: 1
Date: Fri, 16 Sep 2011 17:42:18 +0000
From: cli...@li...
Subject: clisp: * src/makemake.in (clean5): do not remove modules.h
	twice
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/9f01d9ee196c
changeset: 15546:9f01d9ee196cdd9ad814d56580ad90ca5200b648
user:      Sam Steingold <sd...@po...>
date:      2011-09-14 10:45:54 -0400
description:
* src/makemake.in (clean5): do not remove modules.h twice

diffstat:

 src/ChangeLog   |  4 ++++
 src/makemake.in |  2 +-
 2 files changed, 5 insertions(+), 1 deletions(-)



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

Message: 2
Date: Fri, 16 Sep 2011 17:42:21 +0000
From: cli...@li...
Subject: clisp: * modules/readline/readline.lisp: include rlconf.h for
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/ab6020236b1f
changeset: 15547:ab6020236b1fb6df04aad9c737e3fddee5d75ac4
user:      Sam Steingold <sd...@po...>
date:      2011-09-14 10:58:33 -0400
description:
* modules/readline/readline.lisp: include rlconf.h for
DEFAULT_INPUTRC and SYS_INPUTRC and tilde.h for tilde_expand

diffstat:

 modules/readline/readline.lisp |  7 ++++---
 src/ChangeLog                  |  5 +++++
 2 files changed, 9 insertions(+), 3 deletions(-)



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

Message: 3
Date: Fri, 16 Sep 2011 17:42:22 +0000
From: cli...@li...
Subject: clisp: * src/m4/clisp.m4 (CL_DECOLONIZE): fix the 2011-07-25
	154...
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/8b3ceda575e4
changeset: 15548:8b3ceda575e463aadacf311f421c340965b2b9d6
user:      Sam Steingold <sd...@po...>
date:      2011-09-16 12:24:59 -0400
description:
* src/m4/clisp.m4 (CL_DECOLONIZE): fix the 2011-07-25 15472 patch
which broke the native msys/mingw build
Reported by Dan Stanger <dan...@ie...>
<http://article.gmane.org/gmane.lisp.clisp.devel:22759>

diffstat:

 src/ChangeLog   |  7 +++++++
 src/m4/clisp.m4 |  4 ++--
 2 files changed, 9 insertions(+), 2 deletions(-)



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

Message: 4
Date: Fri, 16 Sep 2011 17:42:24 +0000
From: cli...@li...
Subject: clisp: * src/pathname.d (assure_dir_exists): call
	merge-pathname...
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/cc72fa0c3d35
changeset: 15549:cc72fa0c3d353d44cd5b6da51600a225eaef1946
user:      Sam Steingold <sd...@po...>
date:      2011-09-16 13:29:48 -0400
description:
* src/pathname.d (assure_dir_exists): call merge-pathnames on the
truename to ensure that all truenames have non-NIL version because
a NIL component means "unfilled" (19.2.2.2.1) [bug#3405120]

diffstat:

 src/ChangeLog   |   6 ++++++
 src/NEWS        |   1 +
 src/pathname.d  |  13 +++++++------
 tests/ChangeLog |   4 ++++
 tests/path.tst  |  31 ++++++++++++++++++++++++++++++-
 5 files changed, 48 insertions(+), 7 deletions(-)



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

Message: 5
Date: Fri, 16 Sep 2011 17:42:27 +0000
From: cli...@li...
Subject: clisp: regenerate for decolonize/mingw 15548
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/6afcecc6bb2c
changeset: 15550:6afcecc6bb2c3611193ff23a838639253df1a935
user:      Sam Steingold <sd...@po...>
date:      2011-09-16 13:36:00 -0400
description:
regenerate for decolonize/mingw 15548

diffstat:

 modules/berkeley-db/configure |  361 +++++++++++++-----------
 modules/clx/new-clx/configure |  347 ++++++++++++-----------
 modules/dbus/configure        |  336 ++++++++++++-----------
 modules/dirkey/configure      |  326 ++++++++++++----------
 modules/fastcgi/configure     |  337 ++++++++++++-----------
 modules/gdbm/configure        |  337 ++++++++++++-----------
 modules/gtk2/configure        |  331 ++++++++++++----------
 modules/i18n/configure        |  327 ++++++++++++----------
 modules/libsvm/configure      |  336 ++++++++++++-----------
 modules/oracle/configure      |  334 ++++++++++++-----------
 modules/pari/configure        |  336 ++++++++++++-----------
 modules/pcre/configure        |  337 ++++++++++++-----------
 modules/postgresql/configure  |  341 ++++++++++++-----------
 modules/rawsock/configure     |  342 ++++++++++++-----------
 modules/readline/configure    |  359 +++++++++++++-----------
 modules/regexp/configure      |  341 ++++++++++++-----------
 modules/syscalls/configure    |  417 +++++++++++++++--------------
 modules/zlib/configure        |  335 ++++++++++++-----------
 src/aclocal.m4                |    8 +-
 src/configure                 |  602 ++++++++++++++++++++---------------------
 20 files changed, 3559 insertions(+), 3231 deletions(-)



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

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
http://p.sf.net/sfu/rim-devcon-copy2

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

_______________________________________________
clisp-cvs mailing list
cli...@li...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs


End of clisp-cvs Digest, Vol 64, Issue 1
****************************************

Re: Unable to get clisp to compile in MacPorts

[Andrea D'A. <and...@ma...>]

On Sat, Sep 17, 2011 at 01:59, Yves S. Garret
<you...@gm...> wrote:

> Did this:
> $ make
[…]
> writing test file clisp-test.c
> stdbool.h: No such file or directory

Replace line:
%%   print_file("stdbool.h");

in file src/lispbibl.d with:
%%   print_file("gllib/stdbool.h");

It's on line no. 1214 in 2.49 tarball. I'm not sure why llvm didn't
get HAVE_STDBOOL_H symbol while apple's gcc did on Snow Leopard.


-- 
Andrea

Re: Unable to get clisp to compile in MacPorts

[Yves S. G. <you...@gm...>]

Wow, I'm very surprised at the response.  Many thanks!

I know I've been gone for some time, but work and life did not give me much
free time.  I'll try to address several of the concerns in this thread right
now.

I am running Lion at the moment.

When I tried to compile the 2.49 .tar.bz2 file (with the
--ignore-absence-of-libsigsegv flag, although, I really would want this to
function, it installed fine with MacPorts), this is the output that I get:

I go into src, then open up config.lisp... what am I supposed to do there?

Anyways, since the instructions didn't tell me what to do, I ignored it and
kept going.

Did this:

$ make
.....
intelem.d:414: warning: control reaches end of non-void function
lisparit.d: In function ‘I_to_L’:
intelem.d:330: warning: control reaches end of non-void function
lisparit.d: In function ‘I_to_UL’:
intelem.d:234: warning: control reaches end of non-void function
gcc -I/Users/ysg/Downloads/CLisp/clisp-2.49/src/gllib -g -O2 -W -Wswitch
-Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations
-Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4
-DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES -DNO_GETTEXT -I. -c
i18n.c
gcc -I/Users/ysg/Downloads/CLisp/clisp-2.49/src/gllib -g -O2 -W -Wswitch
-Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations
-Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4
-DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES -DNO_GETTEXT -I. -c
unixaux.c
echo '/* generated from Makefile */' > cflags.h.new
echo '#define CC "gcc"' >> cflags.h.new
echo '#define CFLAGS "-g -O2 -W -Wswitch -Wcomment -Wpointer-arith
-Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare
-Wno-format-nonliteral -O -falign-functions=4 -DUNIX_BINARY_DISTRIB
-DENABLE_UNICODE -DDYNAMIC_MODULES -DNO_GETTEXT -I."' >> cflags.h.new
echo '#define LDFLAGS ""' >> cflags.h.new
echo '#define CLFLAGS ""' >> cflags.h.new
echo '#define LIBS "-lncurses  -liconv  libgnu_cl.a"' >> cflags.h.new
echo '#define CPPFLAGS "-I/Users/ysg/Downloads/CLisp/clisp-2.49/src/gllib"'
>> cflags.h.new
echo '#define CPP "gcc -E"' >> cflags.h.new
echo '#define CXX "g++"' >> cflags.h.new
echo '#define CXXFLAGS ""' >> cflags.h.new
echo '#define X_LIBS "-L/usr/X11/lib -R/usr/X11/lib"' >> cflags.h.new
if cmp cflags.h.new cflags.h > /dev/null 2>&1; then rm -f cflags.h.new; else
mv cflags.h.new cflags.h; fi
touch cflags.h.stamp
gcc -I/Users/ysg/Downloads/CLisp/clisp-2.49/src/gllib -g -O2 -W -Wswitch
-Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations
-Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4
-DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES -DNO_GETTEXT -I. -c
built.c
test -r libgnu_cl.a || ln -s gllib/libgnu.a libgnu_cl.a
gcc -I/Users/ysg/Downloads/CLisp/clisp-2.49/src/gllib -g -O2 -W -Wswitch
-Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations
-Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4
-DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES -DNO_GETTEXT -I.
-DCOMPILE_STANDALONE -O0 -c genclisph.c
genclisph.d: In function ‘main’:
genclisph.d:285: warning: comparison of unsigned expression < 0 is always
false
gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type
-Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O
-falign-functions=4 -DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES
-DNO_GETTEXT -I.  genclisph.o -o genclisph
(echo '#ifndef _CLISP_H' ; echo '#define _CLISP_H' ; echo; echo '/* config.h
*/' ; grep '^#' config.h ) > clisp.h
(echo; echo '/* 'intparam.h' */' ; grep '^#' intparam.h ) >> clisp.h
(echo; echo '/* 'floatparam.h' */' ; grep '^#' floatparam.h ) >> clisp.h
(echo; echo '/* genclisph */' ; ./genclisph clisp-test.c ; echo ; echo
'#endif /* _CLISP_H */') >> clisp.h
writing test file clisp-test.c
stdbool.h: No such file or directory
gcc -I/Users/ysg/Downloads/CLisp/clisp-2.49/src/gllib -g -O2 -W -Wswitch
-Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations
-Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4
-DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES -DNO_GETTEXT -I.
 -DUSE_CLISP_H=1 -DCOMPILE_STANDALONE clisp-test.c -o clisp-test-clisp
clisp-test.c: In function ‘main’:
clisp-test.c:18: error: expected declaration or statement at end of input
make: *** [clisp.h] Error 1

Unfortunately I did not have much time to really dig into this.

This is what I get when I compile from the head.

I got the same error about not having libsigsegv... bummer.

I configure again without this library.

$ make
............
depbase=`echo stat.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl   -g -O2 -W -Wswitch -Wcomment
-Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations
-Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4
-DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES -DNO_GETTEXT
 -fno-common -DPIC  -MT stat.o -MD -MP -MF $depbase.Tpo -c -o stat.o stat.c
&&\
mv -f $depbase.Tpo $depbase.Po
depbase=`echo strerror_r.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl   -g -O2 -W -Wswitch -Wcomment
-Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations
-Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4
-DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES -DNO_GETTEXT
 -fno-common -DPIC  -MT strerror_r.o -MD -MP -MF $depbase.Tpo -c -o
strerror_r.o strerror_r.c &&\
mv -f $depbase.Tpo $depbase.Po
depbase=`echo strverscmp.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\
gcc -DHAVE_CONFIG_H -I. -I..  -I../intl   -g -O2 -W -Wswitch -Wcomment
-Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations
-Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4
-DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES -DNO_GETTEXT
 -fno-common -DPIC  -MT strverscmp.o -MD -MP -MF $depbase.Tpo -c -o
strverscmp.o strverscmp.c &&\
mv -f $depbase.Tpo $depbase.Po
rm -f libgnu.a
ar cru libgnu.a c-ctype.o fd-hook.o localcharset.o glthread/lock.o malloca.o
sockets.o strftime.o strnlen1.o tempname.o glthread/threadlib.o
uniname/uniname.o uniwidth/width.o fnmatch.o ioctl.o lstat.o mkfifo.o
mknod.o mktime.o readlink.o regex.o setenv.o stat.o strerror-override.o
strerror_r.o strverscmp.o
/usr/bin/ranlib: file: libgnu.a(fd-hook.o) has no symbols
/usr/bin/ranlib: file: libgnu.a(threadlib.o) has no symbols
ranlib libgnu.a
ranlib: file: libgnu.a(fd-hook.o) has no symbols
ranlib: file: libgnu.a(threadlib.o) has no symbols
sh config.status --header=config.h
config.status: creating config.h
config.status: config.h is unchanged
touch config.h
echo '#include "config.h"' > tmp.c
cat 'intparam.c' >> tmp.c
gcc tmp.c -o intparam
./intparam intparam.h
rm -f intparam tmp.c
echo '#include "config.h"' > tmp.c
cat 'floatparam.c' >> tmp.c
gcc tmp.c -o floatparam
./floatparam floatparam.h
rm -f floatparam tmp.c
gcc -I/Users/ysg/Downloads/CLisp/clisp/src/gllib -g -O2 -W -Wswitch
-Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations
-Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4
-DUNIX_BINARY_DISTRIB -DENABLE_UNICODE -DDYNAMIC_MODULES -DNO_GETTEXT
 ../utils/comment5.c -o comment5
In file included from /usr/include/sys/time.h:198,
                 from
/Users/ysg/Downloads/CLisp/clisp/src/gllib/sys/time.h:39,
                 from
/Users/ysg/Downloads/CLisp/clisp/src/gllib/sys/select.h:59,
                 from /usr/include/unistd.h:672,
                 from
/Users/ysg/Downloads/CLisp/clisp/src/gllib/unistd.h:44,
                 from
/Users/ysg/Downloads/CLisp/clisp/src/gllib/stdlib.h:90,
                 from ../utils/comment5.c:29:
/Users/ysg/Downloads/CLisp/clisp/src/gllib/time.h:469: error: expected ‘;’,
‘,’ or ‘)’ before ‘__timer’
/Users/ysg/Downloads/CLisp/clisp/src/gllib/time.h:491: error: expected ‘;’,
‘,’ or ‘)’ before ‘__timer’
make: *** [comment5] Error 1

It seems to be failing for a different file.

On Thu, Sep 15, 2011 at 4:53 AM, Vladimir Tzankov <vtz...@gm...>wrote:

> Hi Yves,
> I regularly build hg head on Mac (Snow Leopard - WITH gcc) without
> problems - both 32 & 64 bit version, with generational GC,
> with/without threads. I do not remember any problems with 2.49 as
> well.
>
> Can you try to build 2.49 not in MacPorts environment? Simply use
> configure script and make. Is there a difference (if not - please try
> hg head as well).
>
> Vladimir
>
> On Wed, Sep 14, 2011 at 11:25 PM, Yves S. Garret
> <you...@gm...> wrote:
> > Hi all.
> > I was trying to get Common Lisp to compile on my Mac using MacPorts.
>  I've
> > run into an issue with getting it to compile.  The version is 2.49.
>  Below
> > you can find the description that I and some other MacPort users are
> running
> > into.
> >
> > https://trac.macports.org/ticket/30338
>

Re: Unable to get clisp to compile in MacPorts

[Vladimir T. <vtz...@gm...>]

On Fri, Sep 16, 2011 at 3:21 AM, Yves S. Garret
<you...@gm...> wrote:
> Stack overflow 2 caught.
> Segmentation violation correctly detected.
> /bin/sh: line 1: 74966 Illegal instruction: 4  ${dir}$tst
> FAIL: stackoverflow2
> ===================
> 1 of 5 tests failed
> ===================

libsigsegv 2.10 passes all tests on Snow Leopard (and clisp builds
fine with it).
I do not have Lion at hand to test with. As for now I think the
problem is libsigsegv incompatibility with Lion.

Can you try to build clisp without libsigsegv (./configure
--ignore-absence-of-libsigsegv ... )?

Vladimir

Re: Readline on mingw

[Sam S. <sd...@gn...>]

> * Dan Stanger <qna...@vr...> [2011-09-15 19:43:28 -0400]:
>
> An explanation of this is found in:
> http://www.mingw.org/wiki/IncludePathHOWTO . Perhaps an addition to
> the unix/platforms document for mingw could explain that in order to
> build in the mingw environment, these paths need to be included either
> by flags to the compiler, by setting environment variables in
> .profile, or installing readline and termcap in the locations in the
> top level mingw directory.

I have never used msys/mingw, so all I can say is
http://www.cygwin.com/acronyms/#PTC
please feel free to submit either unix/INSTALL patch or the patch to
the top-level configure which work for you to the sf patch tracker.
I hope other mingw users (e.g., Yaroslav) will test them and if they
work for others too, I will apply them.

Thanks.

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.04 (natty) X 11.0.11001000
http://www.PetitionOnline.com/tap12009/ http://pmw.org.il
http://thereligionofpeace.com http://jihadwatch.org http://truepeace.org
Just because you're paranoid doesn't mean they AREN'T after you.

[ clisp-Bugs-3405120 ] probe-pathname set :newest version

[SourceForge.net <no...@so...>]

Bugs item #3405120, was opened at 2011-09-06 13:12
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3405120&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: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Gabor Balazs (gabalz)
Assigned to: Sam Steingold (sds)
Summary: probe-pathname set :newest version

Initial Comment:

$ clisp --version
GNU CLISP 2.49 (2010-07-07) (built 3519331083) (memory 3519302729)
Software: GNU C 4.4.5 
gcc -O2 -march=core2 -fomit-frame-pointer -pipe -Wa,--noexecstack -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -I. -Wl,-O1 -Wl,--as-needed  /usr/lib64/libreadline.so -lncurses -ldl /usr/lib64/libavcall.a /usr/lib64/libcallback.a  -L/usr/lib64 -lsigsegv -L/usr/lib64 -lc libgnu_cl.a 
SAFETY=0 TYPECODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libsigsegv 2.8
libreadline 6.1
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 WORD-SIZE=64 PC386 UNIX)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: /usr/lib64/clisp-2.49/
User language: ENGLISH
Machine: X86_64 (X86_64) localhost [127.0.0.1]

The problem:

probe-pathname sets the version field to :NEWEST, and so this pathname is never EQUAL to another one returned by PATHNAME.

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; this should be NIL

(equal (probe-pathname "/tmp/") (pathname "/tmp/"))
NIL

Furthermore, MAKE-PATHNAME does not initializes the VERSION slot in the following case:

(defparameter *path* (probe-pathname "/tmp/"))
*PATH*

(pathname-version (make-pathname :version NIL :defaults *path*))
:NEWEST ; this should be NIL

This workaround can be done, but this is ugly:

(pathname-version (make-pathname :version NIL :name (pathname-name *path*) :defaults *path*))
NIL


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

>Comment By: Sam Steingold (sds)
Date: 2011-09-16 13:45

Message:
ok, now all the truenames have non-nil version

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

Comment By: Sam Steingold (sds)
Date: 2011-09-16 13:45

Message:
thank you for your bug report.
the bug has been fixed in the source tree (mercurial/hg).
you can either wait for the next release (recommended)
or check out the current mercurial tree (see http://clisp.org)
and build CLISP from the sources (be advised that between
releases the source tree is very unstable and may not even build
on your platform).

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-16 01:05

Message:
Hm, I never thought of using MERGE-PATHNAMES with one argument.
It works indeed for file names. But it seems to fail for directory names.

So if
(car (directory "/tmp/*/"))
#P"/tmp/swtlib-64/"

Then
(equalp (merge-pathnames (pathname "/tmp/swtlib-64/")) (car (directory
"/tmp/*/")))
NIL

It happens because MERGE-PATHNAMES _always_ set version to :NEWEST, but
DIRECTORY sets the :NEWEST flag only to files. In case of directories,
DIRECTORY sets NIL version.

This doesn't seem to be good. I think there should be an easy way to
compare pathnames regardless whether they are file or directory pathnames.

          - - - - - - - - - - 

It is also interesting (as I pointed this out before) that CLISP does not
follow the standard in the case below:

(pathname-version (pathname "/tmp/"))
NIL

(pathname-version (merge-pathnames "swtlib-64/" (pathname "/tmp/")))
:NEWEST

But the standard says: "If pathname does not specify a name, then the
version, if not provided, will come from default-pathname, just like the
other components."
See: http://www.lispworks.com/documentation/HyperSpec/Body/f_merge_.htm
So as 
(pathname-name (pathname "/tmp/"))
NIL
the MERGE-PATHNAMES call above should set NIL version instead of :NEWEST.

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

Comment By: Sam Steingold (sds)
Date: 2011-09-15 23:29

Message:
(equalp (pathname "/bin/tr") (car (directory "/bin/*")))
is wrong because you are comparing "parsed pathname" with a "filesystem
pathname".
you should try 
(equalp (merge-pathname (pathname "/bin/tr")) (car (directory "/bin/*")))

:newest appears whenever pathnames are merged (without the default-version
argument). 
this is reasonable, compliant, and useful in some situations.

custom:*parse-namestring-ansi* does a very specific thing only
tangentially related to your question.

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-14 21:41

Message:
The problem with this behaviour is that you cannot compare pathnames with
the equalp function.
I would like to get T for this:

(equalp (pathname "/bin/tr") (car (directory "/bin/*")))
NIL

where
(car (directory "/bin/*"))
#P"/bin/tr"

Setting the custom:*parse-namestring-ansi* didn't changed anything.

(pathname-version (probe-pathname "/bin/tr"))
:NEWEST

So some of the pathname handling functions set version to NIL, some of
them set it to :NEWEST. This is what I call inconsistency.

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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 09:51

Message:
1. set *parse-namestring-ansi* to T so that symbols are not treated as
pathname designators.
in your case when (probe-pathname "nonexistent") returns NIL,
pathname-version converts it to a pathname with NIL version. see
<http://clisp.org/impnotes/filename-misc.html#parsename>

2. from what I can see, clisp always returns :newest for versions of
truenames. I don't see any problems with that. 

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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 09:51

Message:
1. set *parse-namestring-ansi* to T so that symbols are not treated as
pathname designators.
in your case when (probe-pathname "nonexistent") returns NIL,
pathname-version converts it to a pathname with NIL version. see
<http://clisp.org/impnotes/filename-misc.html#parsename>

2. from what I can see, clisp always returns :newest for versions of
truenames. I don't see any problems with that. 

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-13 19:38

Message:
I see your point, but I think there are still problems.

Problem #1:

http://www.lispworks.com/documentation/HyperSpec/Body/f_merge_.htm
The standard says: "If pathname does not specify a name, then the version,
if not provided, will come from default-pathname, just like the other
components."

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; so this should be NIL

as fortunately
(pathname-version "/tmp/")
NIL

Problem #2: 

(pathname-version (probe-pathname "/tmp/file"))
NIL

(pathname-version (probe-pathname "/tmp/dir/"))
NIL

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; should be NIL

I think CLISP should be consistent here. Why does it return :NEWEST in the
last case?

Problem #3:

(pathname-version (car (directory "/tmp/*/")))
NIL

(pathname-version (car (directory "/tmp/*")))
:NEWEST

Is there any way to let CLISP's directory function return NIL in this last
case?
Otherwise I have to convert all the file pathnames if I want consistency.
Eg, I want to compare pathnames with the equal function.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 18:39

Message:
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_merge-pathnames.html
default-version---a valid pathname version. The default is :newest

i.e., whenever pathnames are merged without an explicit default-version
argument, 
the result will have the :newest version unless the original pathnames
have non-trivial versions
which is unlikely because no modern filesystem has a notion of a version
built-in.

i.e., the behavior you are complaining about is mandated by the standard.
moreover, it is at least somewhat useful because it lets you know whether
the pathname is a result of a merge with *default-pathname-defaults* or of
raw parsing.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 18:39

Message:
This bug report is now marked as "pending"/"invalid".
This means that we think that the problem you report is not a problem with
CLISP.
Unless you - the reporter - act within 2 weeks, the bug will be
permanently closed.
Sorry about the inconvenience - we hope your silence means that you agree
that this is not a bug in CLISP.

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 17:23

Message:
Furthermore,

(pathname-version (pathname "/tmp/"))
NIL ; ok
(pathname-version (pathname "dir/"))
NIL ; ok
(pathname-version (pathname "file"))
NIL ; ok

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; should be NIL!
(pathname-version (merge-pathnames "file" "/tmp/"))
:NEWEST ; should be NIL!


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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 16:31

Message:
Unfortunately, there is even more related bugs like this.

(length (directory "/tmp/*/"))
13

(length (directory "/tmp/*"))
7

So my /tmp directory has files and directories too, then:

(pathname-version (car (directory "/tmp/*/")))
NIL ; correct

(pathname-version (car (directory "/tmp/*")))
:NEWEST ; should be NIL!

But the file pathname creation seems to be good

(pathname-version (pathname "does-not-exist.dne"))
NIL


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

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

Re: mingw cl_cv_decolonize

[Sam S. <sd...@gn...>]

> * Dan Stanger <qna...@vr...> [2011-09-16 06:58:52 -0400]:
>
> It seems that cl_cv_decolonize is defined as 'cygpath --unix $x' when 
> building under mingw. This causes the top level makefile and module 
> configure's to have a cygdrive prefix in paths, which are incorrect in a 
> mingw system.

fixed, thanks.

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.04 (natty) X 11.0.11001000
http://www.PetitionOnline.com/tap12009/ http://iris.org.il http://ffii.org
http://truepeace.org http://mideasttruth.com http://thereligionofpeace.com
Lisp: it's here to save your butt.

mingw cl_cv_decolonize

[Dan S. <dan...@ie...>]

Hello All,
It seems that cl_cv_decolonize is defined as 'cygpath --unix $x' when 
building under mingw. This causes the top level makefile and module 
configure's to have a cygdrive prefix in paths, which are incorrect in a 
mingw system.
For example cl_cv_clisp_libdir is defined as 
/cygdrive/e/MinGW/msys/1.0/home/DanStanger/clisp-hg/mgwbuild/ when it 
should be defined as:
cl_cv_clisp_libdir=/e/MinGW/msys/1.0/home/DanStanger/clisp-hg/mgwbuild/ .
This causes the i18n configure to fail.
Dan Stanger

[ clisp-Bugs-3405120 ] probe-pathname set :newest version

[SourceForge.net <no...@so...>]

Bugs item #3405120, was opened at 2011-09-06 11:12
Message generated for change (Comment added) made by gabalz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3405120&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: Invalid
Priority: 5
Private: No
Submitted By: Gabor Balazs (gabalz)
Assigned to: Sam Steingold (sds)
Summary: probe-pathname set :newest version

Initial Comment:

$ clisp --version
GNU CLISP 2.49 (2010-07-07) (built 3519331083) (memory 3519302729)
Software: GNU C 4.4.5 
gcc -O2 -march=core2 -fomit-frame-pointer -pipe -Wa,--noexecstack -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -I. -Wl,-O1 -Wl,--as-needed  /usr/lib64/libreadline.so -lncurses -ldl /usr/lib64/libavcall.a /usr/lib64/libcallback.a  -L/usr/lib64 -lsigsegv -L/usr/lib64 -lc libgnu_cl.a 
SAFETY=0 TYPECODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libsigsegv 2.8
libreadline 6.1
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 WORD-SIZE=64 PC386 UNIX)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: /usr/lib64/clisp-2.49/
User language: ENGLISH
Machine: X86_64 (X86_64) localhost [127.0.0.1]

The problem:

probe-pathname sets the version field to :NEWEST, and so this pathname is never EQUAL to another one returned by PATHNAME.

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; this should be NIL

(equal (probe-pathname "/tmp/") (pathname "/tmp/"))
NIL

Furthermore, MAKE-PATHNAME does not initializes the VERSION slot in the following case:

(defparameter *path* (probe-pathname "/tmp/"))
*PATH*

(pathname-version (make-pathname :version NIL :defaults *path*))
:NEWEST ; this should be NIL

This workaround can be done, but this is ugly:

(pathname-version (make-pathname :version NIL :name (pathname-name *path*) :defaults *path*))
NIL


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

>Comment By: Gabor Balazs (gabalz)
Date: 2011-09-15 23:05

Message:
Hm, I never thought of using MERGE-PATHNAMES with one argument.
It works indeed for file names. But it seems to fail for directory names.

So if
(car (directory "/tmp/*/"))
#P"/tmp/swtlib-64/"

Then
(equalp (merge-pathnames (pathname "/tmp/swtlib-64/")) (car (directory
"/tmp/*/")))
NIL

It happens because MERGE-PATHNAMES _always_ set version to :NEWEST, but
DIRECTORY sets the :NEWEST flag only to files. In case of directories,
DIRECTORY sets NIL version.

This doesn't seem to be good. I think there should be an easy way to
compare pathnames regardless whether they are file or directory pathnames.

          - - - - - - - - - - 

It is also interesting (as I pointed this out before) that CLISP does not
follow the standard in the case below:

(pathname-version (pathname "/tmp/"))
NIL

(pathname-version (merge-pathnames "swtlib-64/" (pathname "/tmp/")))
:NEWEST

But the standard says: "If pathname does not specify a name, then the
version, if not provided, will come from default-pathname, just like the
other components."
See: http://www.lispworks.com/documentation/HyperSpec/Body/f_merge_.htm
So as 
(pathname-name (pathname "/tmp/"))
NIL
the MERGE-PATHNAMES call above should set NIL version instead of :NEWEST.

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

Comment By: Sam Steingold (sds)
Date: 2011-09-15 21:29

Message:
(equalp (pathname "/bin/tr") (car (directory "/bin/*")))
is wrong because you are comparing "parsed pathname" with a "filesystem
pathname".
you should try 
(equalp (merge-pathname (pathname "/bin/tr")) (car (directory "/bin/*")))

:newest appears whenever pathnames are merged (without the default-version
argument). 
this is reasonable, compliant, and useful in some situations.

custom:*parse-namestring-ansi* does a very specific thing only
tangentially related to your question.

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-14 19:41

Message:
The problem with this behaviour is that you cannot compare pathnames with
the equalp function.
I would like to get T for this:

(equalp (pathname "/bin/tr") (car (directory "/bin/*")))
NIL

where
(car (directory "/bin/*"))
#P"/bin/tr"

Setting the custom:*parse-namestring-ansi* didn't changed anything.

(pathname-version (probe-pathname "/bin/tr"))
:NEWEST

So some of the pathname handling functions set version to NIL, some of
them set it to :NEWEST. This is what I call inconsistency.

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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 07:51

Message:
1. set *parse-namestring-ansi* to T so that symbols are not treated as
pathname designators.
in your case when (probe-pathname "nonexistent") returns NIL,
pathname-version converts it to a pathname with NIL version. see
<http://clisp.org/impnotes/filename-misc.html#parsename>

2. from what I can see, clisp always returns :newest for versions of
truenames. I don't see any problems with that. 

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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 07:51

Message:
1. set *parse-namestring-ansi* to T so that symbols are not treated as
pathname designators.
in your case when (probe-pathname "nonexistent") returns NIL,
pathname-version converts it to a pathname with NIL version. see
<http://clisp.org/impnotes/filename-misc.html#parsename>

2. from what I can see, clisp always returns :newest for versions of
truenames. I don't see any problems with that. 

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-13 17:38

Message:
I see your point, but I think there are still problems.

Problem #1:

http://www.lispworks.com/documentation/HyperSpec/Body/f_merge_.htm
The standard says: "If pathname does not specify a name, then the version,
if not provided, will come from default-pathname, just like the other
components."

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; so this should be NIL

as fortunately
(pathname-version "/tmp/")
NIL

Problem #2: 

(pathname-version (probe-pathname "/tmp/file"))
NIL

(pathname-version (probe-pathname "/tmp/dir/"))
NIL

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; should be NIL

I think CLISP should be consistent here. Why does it return :NEWEST in the
last case?

Problem #3:

(pathname-version (car (directory "/tmp/*/")))
NIL

(pathname-version (car (directory "/tmp/*")))
:NEWEST

Is there any way to let CLISP's directory function return NIL in this last
case?
Otherwise I have to convert all the file pathnames if I want consistency.
Eg, I want to compare pathnames with the equal function.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 16:39

Message:
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_merge-pathnames.html
default-version---a valid pathname version. The default is :newest

i.e., whenever pathnames are merged without an explicit default-version
argument, 
the result will have the :newest version unless the original pathnames
have non-trivial versions
which is unlikely because no modern filesystem has a notion of a version
built-in.

i.e., the behavior you are complaining about is mandated by the standard.
moreover, it is at least somewhat useful because it lets you know whether
the pathname is a result of a merge with *default-pathname-defaults* or of
raw parsing.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 16:39

Message:
This bug report is now marked as "pending"/"invalid".
This means that we think that the problem you report is not a problem with
CLISP.
Unless you - the reporter - act within 2 weeks, the bug will be
permanently closed.
Sorry about the inconvenience - we hope your silence means that you agree
that this is not a bug in CLISP.

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 15:23

Message:
Furthermore,

(pathname-version (pathname "/tmp/"))
NIL ; ok
(pathname-version (pathname "dir/"))
NIL ; ok
(pathname-version (pathname "file"))
NIL ; ok

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; should be NIL!
(pathname-version (merge-pathnames "file" "/tmp/"))
:NEWEST ; should be NIL!


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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 14:31

Message:
Unfortunately, there is even more related bugs like this.

(length (directory "/tmp/*/"))
13

(length (directory "/tmp/*"))
7

So my /tmp directory has files and directories too, then:

(pathname-version (car (directory "/tmp/*/")))
NIL ; correct

(pathname-version (car (directory "/tmp/*")))
:NEWEST ; should be NIL!

But the file pathname creation seems to be good

(pathname-version (pathname "does-not-exist.dne"))
NIL


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

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

[ clisp-Bugs-3405120 ] probe-pathname set :newest version

[SourceForge.net <no...@so...>]

Bugs item #3405120, was opened at 2011-09-06 13:12
Message generated for change (Settings changed) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3405120&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: Pending
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Gabor Balazs (gabalz)
Assigned to: Sam Steingold (sds)
Summary: probe-pathname set :newest version

Initial Comment:

$ clisp --version
GNU CLISP 2.49 (2010-07-07) (built 3519331083) (memory 3519302729)
Software: GNU C 4.4.5 
gcc -O2 -march=core2 -fomit-frame-pointer -pipe -Wa,--noexecstack -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -I. -Wl,-O1 -Wl,--as-needed  /usr/lib64/libreadline.so -lncurses -ldl /usr/lib64/libavcall.a /usr/lib64/libcallback.a  -L/usr/lib64 -lsigsegv -L/usr/lib64 -lc libgnu_cl.a 
SAFETY=0 TYPECODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libsigsegv 2.8
libreadline 6.1
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 WORD-SIZE=64 PC386 UNIX)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: /usr/lib64/clisp-2.49/
User language: ENGLISH
Machine: X86_64 (X86_64) localhost [127.0.0.1]

The problem:

probe-pathname sets the version field to :NEWEST, and so this pathname is never EQUAL to another one returned by PATHNAME.

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; this should be NIL

(equal (probe-pathname "/tmp/") (pathname "/tmp/"))
NIL

Furthermore, MAKE-PATHNAME does not initializes the VERSION slot in the following case:

(defparameter *path* (probe-pathname "/tmp/"))
*PATH*

(pathname-version (make-pathname :version NIL :defaults *path*))
:NEWEST ; this should be NIL

This workaround can be done, but this is ugly:

(pathname-version (make-pathname :version NIL :name (pathname-name *path*) :defaults *path*))
NIL


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

>Comment By: Sam Steingold (sds)
Date: 2011-09-15 23:29

Message:
(equalp (pathname "/bin/tr") (car (directory "/bin/*")))
is wrong because you are comparing "parsed pathname" with a "filesystem
pathname".
you should try 
(equalp (merge-pathname (pathname "/bin/tr")) (car (directory "/bin/*")))

:newest appears whenever pathnames are merged (without the default-version
argument). 
this is reasonable, compliant, and useful in some situations.

custom:*parse-namestring-ansi* does a very specific thing only
tangentially related to your question.

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-14 21:41

Message:
The problem with this behaviour is that you cannot compare pathnames with
the equalp function.
I would like to get T for this:

(equalp (pathname "/bin/tr") (car (directory "/bin/*")))
NIL

where
(car (directory "/bin/*"))
#P"/bin/tr"

Setting the custom:*parse-namestring-ansi* didn't changed anything.

(pathname-version (probe-pathname "/bin/tr"))
:NEWEST

So some of the pathname handling functions set version to NIL, some of
them set it to :NEWEST. This is what I call inconsistency.

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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 09:51

Message:
1. set *parse-namestring-ansi* to T so that symbols are not treated as
pathname designators.
in your case when (probe-pathname "nonexistent") returns NIL,
pathname-version converts it to a pathname with NIL version. see
<http://clisp.org/impnotes/filename-misc.html#parsename>

2. from what I can see, clisp always returns :newest for versions of
truenames. I don't see any problems with that. 

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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 09:51

Message:
1. set *parse-namestring-ansi* to T so that symbols are not treated as
pathname designators.
in your case when (probe-pathname "nonexistent") returns NIL,
pathname-version converts it to a pathname with NIL version. see
<http://clisp.org/impnotes/filename-misc.html#parsename>

2. from what I can see, clisp always returns :newest for versions of
truenames. I don't see any problems with that. 

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-13 19:38

Message:
I see your point, but I think there are still problems.

Problem #1:

http://www.lispworks.com/documentation/HyperSpec/Body/f_merge_.htm
The standard says: "If pathname does not specify a name, then the version,
if not provided, will come from default-pathname, just like the other
components."

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; so this should be NIL

as fortunately
(pathname-version "/tmp/")
NIL

Problem #2: 

(pathname-version (probe-pathname "/tmp/file"))
NIL

(pathname-version (probe-pathname "/tmp/dir/"))
NIL

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; should be NIL

I think CLISP should be consistent here. Why does it return :NEWEST in the
last case?

Problem #3:

(pathname-version (car (directory "/tmp/*/")))
NIL

(pathname-version (car (directory "/tmp/*")))
:NEWEST

Is there any way to let CLISP's directory function return NIL in this last
case?
Otherwise I have to convert all the file pathnames if I want consistency.
Eg, I want to compare pathnames with the equal function.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 18:39

Message:
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_merge-pathnames.html
default-version---a valid pathname version. The default is :newest

i.e., whenever pathnames are merged without an explicit default-version
argument, 
the result will have the :newest version unless the original pathnames
have non-trivial versions
which is unlikely because no modern filesystem has a notion of a version
built-in.

i.e., the behavior you are complaining about is mandated by the standard.
moreover, it is at least somewhat useful because it lets you know whether
the pathname is a result of a merge with *default-pathname-defaults* or of
raw parsing.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 18:39

Message:
This bug report is now marked as "pending"/"invalid".
This means that we think that the problem you report is not a problem with
CLISP.
Unless you - the reporter - act within 2 weeks, the bug will be
permanently closed.
Sorry about the inconvenience - we hope your silence means that you agree
that this is not a bug in CLISP.

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 17:23

Message:
Furthermore,

(pathname-version (pathname "/tmp/"))
NIL ; ok
(pathname-version (pathname "dir/"))
NIL ; ok
(pathname-version (pathname "file"))
NIL ; ok

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; should be NIL!
(pathname-version (merge-pathnames "file" "/tmp/"))
:NEWEST ; should be NIL!


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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 16:31

Message:
Unfortunately, there is even more related bugs like this.

(length (directory "/tmp/*/"))
13

(length (directory "/tmp/*"))
7

So my /tmp directory has files and directories too, then:

(pathname-version (car (directory "/tmp/*/")))
NIL ; correct

(pathname-version (car (directory "/tmp/*")))
:NEWEST ; should be NIL!

But the file pathname creation seems to be good

(pathname-version (pathname "does-not-exist.dne"))
NIL


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

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

Re: Delivery Status Notification (Failure)

[Yves S. G. <you...@gm...>]

Hey guys, I keep getting this error message every time I write back to
cli...@li..., what gives?

On Thu, Sep 15, 2011 at 9:40 PM, <pos...@st...> wrote:

> This is an automatically generated Delivery Status Notification.
>
> Delivery to the following recipients failed.
>
>       sh...@st...
>
>
>
>
> Final-Recipient: rfc822;sh...@st...
> Action: failed
> Status: 5.2.1
> X-Display-Name: Shiyas Rasheed
>
>
>
> ---------- Forwarded message ----------
> From: "Yves S. Garret" <you...@gm...>
> To: Vladimir Tzankov <vtz...@gm...>, clisp-devel <
> cli...@li...>
> Date: Thu, 15 Sep 2011 20:21:53 -0400
> Subject: Re: Unable to get clisp to compile in MacPorts
> Yeah, doesn't really work.  I now know what libsigsegv does and it's a
> really nice to have.  Here is what I did:
> * I got 2.49 and unzipped it.
> * Went in there and did ./configure.  It warned me that it did not detect
> libsigsegv and told me how to install it (even though it's already installed
> via MacPorts.)
> * I went through the listed steps to install libsigsegv:
>   mkdir tools; cd tools; prefix=`pwd`/x86_64-apple-darwin11.1.0
>   wget http://ftp.gnu.org/gnu/libsigsegv/libsigsegv-2.10.tar.gz
>   tar xfz libsigsegv-2.10.tar.gz
>   cd libsigsegv-2.10
>   ./configure --prefix=${prefix} && make && make check
> * I get to the part about doing make check and this is the output that I
> get:
> % make check
> Making check in src
> make[1]: Nothing to be done for `check'.
> Making check in tests
> make  check-TESTS
> Test passed.
> PASS: sigsegv1
> Test passed.
> PASS: sigsegv2
> Doing SIGSEGV pass 1.
> Stack overflow 1 caught.
> Doing SIGSEGV pass 2.
> Stack overflow 2 caught.
> Test passed.
> PASS: sigsegv3
> Starting recursion pass 1.
> Stack overflow 1 caught.
> Starting recursion pass 2.
> Stack overflow 2 caught.
> Test passed.
> PASS: stackoverflow1
> Starting recursion pass 1.
> Stack overflow 1 caught.
> Starting recursion pass 2.
> Stack overflow 2 caught.
> Segmentation violation correctly detected.
> /bin/sh: line 1: 74966 Illegal instruction: 4  ${dir}$tst
> FAIL: stackoverflow2
> ===================
> 1 of 5 tests failed
> ===================
> make[2]: *** [check-TESTS] Error 1
> make[1]: *** [check-am] Error 2
> make: *** [check-recursive] Error 1
>
> Why is it that stackoverflow2 failing?
>
> What am I doing wrong?
>
> Oh, I have Mac OS Lion, does that matter?
>
> On Thu, Sep 15, 2011 at 5:36 AM, Vladimir Tzankov <vtz...@gm...>wrote:
>
>> yes - sorry. I mean mercurial repository.
>>
>> On Thu, Sep 15, 2011 at 12:26 PM, Yves S. Garret
>> <you...@gm...> wrote:
>> > Vladimir, what do you mean by hg?  Is this a reference to mercurial?
>> >
>> > On Thu, Sep 15, 2011 at 4:53 AM, Vladimir Tzankov <vtz...@gm...>
>> > wrote:
>> >>
>> >> Hi Yves,
>> >> I regularly build hg head on Mac (Snow Leopard - WITH gcc) without
>> >> problems - both 32 & 64 bit version, with generational GC,
>> >> with/without threads. I do not remember any problems with 2.49 as
>> >> well.
>> >>
>> >> Can you try to build 2.49 not in MacPorts environment? Simply use
>> >> configure script and make. Is there a difference (if not - please try
>> >> hg head as well).
>> >>
>> >> Vladimir
>> >>
>> >> On Wed, Sep 14, 2011 at 11:25 PM, Yves S. Garret
>> >> <you...@gm...> wrote:
>> >> > Hi all.
>> >> > I was trying to get Common Lisp to compile on my Mac using MacPorts.
>> >> >  I've
>> >> > run into an issue with getting it to compile.  The version is 2.49.
>> >> >  Below
>> >> > you can find the description that I and some other MacPort users are
>> >> > running
>> >> > into.
>> >> >
>> >> > https://trac.macports.org/ticket/30338
>> >
>> >
>>
>
>
>
> ------------------------------------------------------------------------------
> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
> http://p.sf.net/sfu/rim-devcon-copy2
> _______________________________________________
> clisp-devel mailing list
> cli...@li...
> https://lists.sourceforge.net/lists/listinfo/clisp-devel
>
>

Re: Unable to get clisp to compile in MacPorts

[Yves S. G. <you...@gm...>]

Yeah, doesn't really work.  I now know what libsigsegv does and it's a
really nice to have.  Here is what I did:
* I got 2.49 and unzipped it.
* Went in there and did ./configure.  It warned me that it did not detect
libsigsegv and told me how to install it (even though it's already installed
via MacPorts.)
* I went through the listed steps to install libsigsegv:
  mkdir tools; cd tools; prefix=`pwd`/x86_64-apple-darwin11.1.0
  wget http://ftp.gnu.org/gnu/libsigsegv/libsigsegv-2.10.tar.gz
  tar xfz libsigsegv-2.10.tar.gz
  cd libsigsegv-2.10
  ./configure --prefix=${prefix} && make && make check
* I get to the part about doing make check and this is the output that I
get:
% make check
Making check in src
make[1]: Nothing to be done for `check'.
Making check in tests
make  check-TESTS
Test passed.
PASS: sigsegv1
Test passed.
PASS: sigsegv2
Doing SIGSEGV pass 1.
Stack overflow 1 caught.
Doing SIGSEGV pass 2.
Stack overflow 2 caught.
Test passed.
PASS: sigsegv3
Starting recursion pass 1.
Stack overflow 1 caught.
Starting recursion pass 2.
Stack overflow 2 caught.
Test passed.
PASS: stackoverflow1
Starting recursion pass 1.
Stack overflow 1 caught.
Starting recursion pass 2.
Stack overflow 2 caught.
Segmentation violation correctly detected.
/bin/sh: line 1: 74966 Illegal instruction: 4  ${dir}$tst
FAIL: stackoverflow2
===================
1 of 5 tests failed
===================
make[2]: *** [check-TESTS] Error 1
make[1]: *** [check-am] Error 2
make: *** [check-recursive] Error 1

Why is it that stackoverflow2 failing?

What am I doing wrong?

Oh, I have Mac OS Lion, does that matter?

On Thu, Sep 15, 2011 at 5:36 AM, Vladimir Tzankov <vtz...@gm...>wrote:

> yes - sorry. I mean mercurial repository.
>
> On Thu, Sep 15, 2011 at 12:26 PM, Yves S. Garret
> <you...@gm...> wrote:
> > Vladimir, what do you mean by hg?  Is this a reference to mercurial?
> >
> > On Thu, Sep 15, 2011 at 4:53 AM, Vladimir Tzankov <vtz...@gm...>
> > wrote:
> >>
> >> Hi Yves,
> >> I regularly build hg head on Mac (Snow Leopard - WITH gcc) without
> >> problems - both 32 & 64 bit version, with generational GC,
> >> with/without threads. I do not remember any problems with 2.49 as
> >> well.
> >>
> >> Can you try to build 2.49 not in MacPorts environment? Simply use
> >> configure script and make. Is there a difference (if not - please try
> >> hg head as well).
> >>
> >> Vladimir
> >>
> >> On Wed, Sep 14, 2011 at 11:25 PM, Yves S. Garret
> >> <you...@gm...> wrote:
> >> > Hi all.
> >> > I was trying to get Common Lisp to compile on my Mac using MacPorts.
> >> >  I've
> >> > run into an issue with getting it to compile.  The version is 2.49.
> >> >  Below
> >> > you can find the description that I and some other MacPort users are
> >> > running
> >> > into.
> >> >
> >> > https://trac.macports.org/ticket/30338
> >
> >
>

Re: Readline on mingw

[Dan S. <dan...@ie...>]

The mingw environment, does not put /usr/include and /usr/local/include 
in the include paths, and /usr/lib and /usr/local/lib in the library 
search paths.
An explanation of this is found in: 
http://www.mingw.org/wiki/IncludePathHOWTO . Perhaps an addition to the 
unix/platforms document for mingw could explain that in order to build 
in the mingw environment, these paths need to be included either by 
flags to the compiler, by setting environment variables in .profile, or 
installing readline and termcap in the locations in the top level mingw 
directory.

Dan Stanger

Re: Unable to get clisp to compile in MacPorts

[Yves S. G. <you...@gm...>]

What role does libsigsegv play in clisp?  And what is it?

On Thu, Sep 15, 2011 at 5:36 AM, Vladimir Tzankov <vtz...@gm...>wrote:

> yes - sorry. I mean mercurial repository.
>
> On Thu, Sep 15, 2011 at 12:26 PM, Yves S. Garret
> <you...@gm...> wrote:
> > Vladimir, what do you mean by hg?  Is this a reference to mercurial?
> >
> > On Thu, Sep 15, 2011 at 4:53 AM, Vladimir Tzankov <vtz...@gm...>
> > wrote:
> >>
> >> Hi Yves,
> >> I regularly build hg head on Mac (Snow Leopard - WITH gcc) without
> >> problems - both 32 & 64 bit version, with generational GC,
> >> with/without threads. I do not remember any problems with 2.49 as
> >> well.
> >>
> >> Can you try to build 2.49 not in MacPorts environment? Simply use
> >> configure script and make. Is there a difference (if not - please try
> >> hg head as well).
> >>
> >> Vladimir
> >>
> >> On Wed, Sep 14, 2011 at 11:25 PM, Yves S. Garret
> >> <you...@gm...> wrote:
> >> > Hi all.
> >> > I was trying to get Common Lisp to compile on my Mac using MacPorts.
> >> >  I've
> >> > run into an issue with getting it to compile.  The version is 2.49.
> >> >  Below
> >> > you can find the description that I and some other MacPort users are
> >> > running
> >> > into.
> >> >
> >> > https://trac.macports.org/ticket/30338
> >
> >
>

Re: Unable to get clisp to compile in MacPorts

[Vladimir T. <vtz...@gm...>]

Hi Yves,
I regularly build hg head on Mac (Snow Leopard - WITH gcc) without
problems - both 32 & 64 bit version, with generational GC,
with/without threads. I do not remember any problems with 2.49 as
well.

Can you try to build 2.49 not in MacPorts environment? Simply use
configure script and make. Is there a difference (if not - please try
hg head as well).

Vladimir

On Wed, Sep 14, 2011 at 11:25 PM, Yves S. Garret
<you...@gm...> wrote:
> Hi all.
> I was trying to get Common Lisp to compile on my Mac using MacPorts.  I've
> run into an issue with getting it to compile.  The version is 2.49.  Below
> you can find the description that I and some other MacPort users are running
> into.
>
> https://trac.macports.org/ticket/30338

[ clisp-Bugs-3405120 ] probe-pathname set :newest version

[SourceForge.net <no...@so...>]

Bugs item #3405120, was opened at 2011-09-06 11:12
Message generated for change (Comment added) made by gabalz
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3405120&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: Invalid
Priority: 5
Private: No
Submitted By: Gabor Balazs (gabalz)
Assigned to: Sam Steingold (sds)
Summary: probe-pathname set :newest version

Initial Comment:

$ clisp --version
GNU CLISP 2.49 (2010-07-07) (built 3519331083) (memory 3519302729)
Software: GNU C 4.4.5 
gcc -O2 -march=core2 -fomit-frame-pointer -pipe -Wa,--noexecstack -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -I. -Wl,-O1 -Wl,--as-needed  /usr/lib64/libreadline.so -lncurses -ldl /usr/lib64/libavcall.a /usr/lib64/libcallback.a  -L/usr/lib64 -lsigsegv -L/usr/lib64 -lc libgnu_cl.a 
SAFETY=0 TYPECODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libsigsegv 2.8
libreadline 6.1
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 WORD-SIZE=64 PC386 UNIX)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: /usr/lib64/clisp-2.49/
User language: ENGLISH
Machine: X86_64 (X86_64) localhost [127.0.0.1]

The problem:

probe-pathname sets the version field to :NEWEST, and so this pathname is never EQUAL to another one returned by PATHNAME.

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; this should be NIL

(equal (probe-pathname "/tmp/") (pathname "/tmp/"))
NIL

Furthermore, MAKE-PATHNAME does not initializes the VERSION slot in the following case:

(defparameter *path* (probe-pathname "/tmp/"))
*PATH*

(pathname-version (make-pathname :version NIL :defaults *path*))
:NEWEST ; this should be NIL

This workaround can be done, but this is ugly:

(pathname-version (make-pathname :version NIL :name (pathname-name *path*) :defaults *path*))
NIL


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

>Comment By: Gabor Balazs (gabalz)
Date: 2011-09-14 19:41

Message:
The problem with this behaviour is that you cannot compare pathnames with
the equalp function.
I would like to get T for this:

(equalp (pathname "/bin/tr") (car (directory "/bin/*")))
NIL

where
(car (directory "/bin/*"))
#P"/bin/tr"

Setting the custom:*parse-namestring-ansi* didn't changed anything.

(pathname-version (probe-pathname "/bin/tr"))
:NEWEST

So some of the pathname handling functions set version to NIL, some of
them set it to :NEWEST. This is what I call inconsistency.

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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 07:51

Message:
1. set *parse-namestring-ansi* to T so that symbols are not treated as
pathname designators.
in your case when (probe-pathname "nonexistent") returns NIL,
pathname-version converts it to a pathname with NIL version. see
<http://clisp.org/impnotes/filename-misc.html#parsename>

2. from what I can see, clisp always returns :newest for versions of
truenames. I don't see any problems with that. 

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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 07:51

Message:
1. set *parse-namestring-ansi* to T so that symbols are not treated as
pathname designators.
in your case when (probe-pathname "nonexistent") returns NIL,
pathname-version converts it to a pathname with NIL version. see
<http://clisp.org/impnotes/filename-misc.html#parsename>

2. from what I can see, clisp always returns :newest for versions of
truenames. I don't see any problems with that. 

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-13 17:38

Message:
I see your point, but I think there are still problems.

Problem #1:

http://www.lispworks.com/documentation/HyperSpec/Body/f_merge_.htm
The standard says: "If pathname does not specify a name, then the version,
if not provided, will come from default-pathname, just like the other
components."

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; so this should be NIL

as fortunately
(pathname-version "/tmp/")
NIL

Problem #2: 

(pathname-version (probe-pathname "/tmp/file"))
NIL

(pathname-version (probe-pathname "/tmp/dir/"))
NIL

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; should be NIL

I think CLISP should be consistent here. Why does it return :NEWEST in the
last case?

Problem #3:

(pathname-version (car (directory "/tmp/*/")))
NIL

(pathname-version (car (directory "/tmp/*")))
:NEWEST

Is there any way to let CLISP's directory function return NIL in this last
case?
Otherwise I have to convert all the file pathnames if I want consistency.
Eg, I want to compare pathnames with the equal function.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 16:39

Message:
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_merge-pathnames.html
default-version---a valid pathname version. The default is :newest

i.e., whenever pathnames are merged without an explicit default-version
argument, 
the result will have the :newest version unless the original pathnames
have non-trivial versions
which is unlikely because no modern filesystem has a notion of a version
built-in.

i.e., the behavior you are complaining about is mandated by the standard.
moreover, it is at least somewhat useful because it lets you know whether
the pathname is a result of a merge with *default-pathname-defaults* or of
raw parsing.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 16:39

Message:
This bug report is now marked as "pending"/"invalid".
This means that we think that the problem you report is not a problem with
CLISP.
Unless you - the reporter - act within 2 weeks, the bug will be
permanently closed.
Sorry about the inconvenience - we hope your silence means that you agree
that this is not a bug in CLISP.

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 15:23

Message:
Furthermore,

(pathname-version (pathname "/tmp/"))
NIL ; ok
(pathname-version (pathname "dir/"))
NIL ; ok
(pathname-version (pathname "file"))
NIL ; ok

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; should be NIL!
(pathname-version (merge-pathnames "file" "/tmp/"))
:NEWEST ; should be NIL!


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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 14:31

Message:
Unfortunately, there is even more related bugs like this.

(length (directory "/tmp/*/"))
13

(length (directory "/tmp/*"))
7

So my /tmp directory has files and directories too, then:

(pathname-version (car (directory "/tmp/*/")))
NIL ; correct

(pathname-version (car (directory "/tmp/*")))
:NEWEST ; should be NIL!

But the file pathname creation seems to be good

(pathname-version (pathname "does-not-exist.dne"))
NIL


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

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

Readline on mingw

[Dan S. <dan...@ie...>]

Hello All,
Sorry if this has been asked before, but is it currently possible for 
the readline libraries to be found by configure by default, using the 
mingw development environment?
If so, where do the libraries and include files need to be installed? In 
searching the list, the references all seem to indicate that a path to 
readline needs to be provided.
Thank you,
Dan Stanger

Unable to get clisp to compile in MacPorts

[Yves S. G. <you...@gm...>]

Hi all.

I was trying to get Common Lisp to compile on my Mac using MacPorts.  I've
run into an issue with getting it to compile.  The version is 2.49.  Below
you can find the description that I and some other MacPort users are running
into.

https://trac.macports.org/ticket/30338

MacPorts gets the file fine, configures it fine, but then proceeds to fail
when building it.

This is the end of the log file describing the issue:

...................................
checking whether getrusage works... (cached) yes
checking whether link(2) dereferences a symlink... (cached) yes
checking whether setpgrp() is POSIX... yes
configure: ** System Calls (output)
configure: updating cache ../config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: creating link.sh
config.status: creating gllib/Makefile
config.status: creating config.h
config.status: executing depfiles commands
configure: ** System Calls (done)
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_clisp/clisp/work/clisp-2.49/src/clisp
-K boot  -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -q -C
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_clisp/clisp/work/clisp-2.49/src/linkkit/modprep
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_clisp/clisp/work/clisp-2.49/modules/syscalls/calls.c
./
;; MODPREP:
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_clisp/clisp/work/clisp-2.49/modules/syscalls/calls.c"
--> #P"calls.m.c"
;; MODPREP: reading
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_clisp/clisp/work/clisp-2.49/modules/syscalls/calls.c":
237,815 bytes, 4,603 lines
WARNING: truncated a very long tag (from 6,146 to 2,000) for
          ("(OR INTEGER (MEMBER"
           ..)

WARNING: truncated a very long tag (from 3,248 to 2,000) for
         ("(OR INTEGER (MEMBER" ..)
WARNING:

 "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_clisp/clisp/work/clisp-2.49/modules/syscalls/calls.c"
         :5632: fixed object case ":ERROR_ITERATED_DATA_EXCEEDS_64k"
WARNING:

 "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_clisp/clisp/work/clisp-2.49/modules/syscalls/calls.c"
         :5632: fixed object case ":ERROR_AUTODATASEG_EXCEEDS_64k"
*** - handle_fault error2 ! address = 0x4 not in [0x7c5df000,0x7c879a74) !
SIGSEGV cannot be cured. Fault address = 0x4.
GC count: 256
Space collected by GC: 0 126994768
Run time: 3 520495
Real time: 4 304425
GC time: 0 797705
Permanently allocated: 87232 bytes.
Currently in use: 4947056 bytes.
Free space: 107 bytes.

*** - handle_fault error2 ! address = 0x54c2000 not in
[0x7c5df000,0x7c879a74) !
SIGSEGV cannot be cured. Fault address = 0x54c2000.
GC count: 256
Space collected by GC: 0 126994768
Run time: 3 520701
Real time: 4 304657
GC time: 0 797705
Permanently allocated: 87232 bytes.
Currently in use: 4947056 bytes.
Free space: 107 bytes.

*** - handle_fault error2 ! address = 0x54c2000 not in
[0x7c5df000,0x7c879a74) !
SIGSEGV cannot be cured. Fault address = 0x54c2000.
GC count: 256
Space collected by GC: 0 126994768
Run time: 3 520796
Real time: 4 304760
GC time: 0 797705
Permanently allocated: 87232 bytes.
Currently in use: 4947056 bytes.
Free space: 107 bytes.

*** - handle_fault error2 ! address = 0x54c2000 not in
[0x7c5df000,0x7c879a74) !
SIGSEGV cannot be cured. Fault address = 0x54c2000.
GC count: 256
Space collected by GC: 0 126994768
Run time: 3 520890
Real time: 4 305133
GC time: 0 797705
Permanently allocated: 87232 bytes.
Currently in use: 4947056 bytes.
Free space: 107 bytes.
make[1]: *** [calls.m.c] Segmentation fault: 11
make: *** [syscalls] Error 2
shell command "cd
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_clisp/clisp/work/clisp-2.49/src
&& ulimit -s 16384 &&  unset LD_PREBIND LD_PREBIND_ALLOW_OVERLAP &&  make"
returned error 2
Error: Target org.macports.build returned: shell command failed (see log for
details)
DEBUG: Backtrace: shell command failed (see log for details)
    while executing
"$procedure $targetname"
Warning: the following items did not execute (for clisp):
org.macports.activate org.macports.build org.macports.destroot
org.macports.install
Log for clisp is at:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_lang_clisp/clisp/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Thoughts?

[ clisp-Bugs-3405120 ] probe-pathname set :newest version

[SourceForge.net <no...@so...>]

Bugs item #3405120, was opened at 2011-09-06 13:12
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3405120&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: Pending
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Gabor Balazs (gabalz)
Assigned to: Sam Steingold (sds)
Summary: probe-pathname set :newest version

Initial Comment:

$ clisp --version
GNU CLISP 2.49 (2010-07-07) (built 3519331083) (memory 3519302729)
Software: GNU C 4.4.5 
gcc -O2 -march=core2 -fomit-frame-pointer -pipe -Wa,--noexecstack -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -I. -Wl,-O1 -Wl,--as-needed  /usr/lib64/libreadline.so -lncurses -ldl /usr/lib64/libavcall.a /usr/lib64/libcallback.a  -L/usr/lib64 -lsigsegv -L/usr/lib64 -lc libgnu_cl.a 
SAFETY=0 TYPECODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libsigsegv 2.8
libreadline 6.1
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 WORD-SIZE=64 PC386 UNIX)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: /usr/lib64/clisp-2.49/
User language: ENGLISH
Machine: X86_64 (X86_64) localhost [127.0.0.1]

The problem:

probe-pathname sets the version field to :NEWEST, and so this pathname is never EQUAL to another one returned by PATHNAME.

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; this should be NIL

(equal (probe-pathname "/tmp/") (pathname "/tmp/"))
NIL

Furthermore, MAKE-PATHNAME does not initializes the VERSION slot in the following case:

(defparameter *path* (probe-pathname "/tmp/"))
*PATH*

(pathname-version (make-pathname :version NIL :defaults *path*))
:NEWEST ; this should be NIL

This workaround can be done, but this is ugly:

(pathname-version (make-pathname :version NIL :name (pathname-name *path*) :defaults *path*))
NIL


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

>Comment By: Sam Steingold (sds)
Date: 2011-09-14 09:51

Message:
1. set *parse-namestring-ansi* to T so that symbols are not treated as
pathname designators.
in your case when (probe-pathname "nonexistent") returns NIL,
pathname-version converts it to a pathname with NIL version. see
<http://clisp.org/impnotes/filename-misc.html#parsename>

2. from what I can see, clisp always returns :newest for versions of
truenames. I don't see any problems with that. 

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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 09:51

Message:
1. set *parse-namestring-ansi* to T so that symbols are not treated as
pathname designators.
in your case when (probe-pathname "nonexistent") returns NIL,
pathname-version converts it to a pathname with NIL version. see
<http://clisp.org/impnotes/filename-misc.html#parsename>

2. from what I can see, clisp always returns :newest for versions of
truenames. I don't see any problems with that. 

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-13 19:38

Message:
I see your point, but I think there are still problems.

Problem #1:

http://www.lispworks.com/documentation/HyperSpec/Body/f_merge_.htm
The standard says: "If pathname does not specify a name, then the version,
if not provided, will come from default-pathname, just like the other
components."

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; so this should be NIL

as fortunately
(pathname-version "/tmp/")
NIL

Problem #2: 

(pathname-version (probe-pathname "/tmp/file"))
NIL

(pathname-version (probe-pathname "/tmp/dir/"))
NIL

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; should be NIL

I think CLISP should be consistent here. Why does it return :NEWEST in the
last case?

Problem #3:

(pathname-version (car (directory "/tmp/*/")))
NIL

(pathname-version (car (directory "/tmp/*")))
:NEWEST

Is there any way to let CLISP's directory function return NIL in this last
case?
Otherwise I have to convert all the file pathnames if I want consistency.
Eg, I want to compare pathnames with the equal function.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 18:39

Message:
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_merge-pathnames.html
default-version---a valid pathname version. The default is :newest

i.e., whenever pathnames are merged without an explicit default-version
argument, 
the result will have the :newest version unless the original pathnames
have non-trivial versions
which is unlikely because no modern filesystem has a notion of a version
built-in.

i.e., the behavior you are complaining about is mandated by the standard.
moreover, it is at least somewhat useful because it lets you know whether
the pathname is a result of a merge with *default-pathname-defaults* or of
raw parsing.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 18:39

Message:
This bug report is now marked as "pending"/"invalid".
This means that we think that the problem you report is not a problem with
CLISP.
Unless you - the reporter - act within 2 weeks, the bug will be
permanently closed.
Sorry about the inconvenience - we hope your silence means that you agree
that this is not a bug in CLISP.

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 17:23

Message:
Furthermore,

(pathname-version (pathname "/tmp/"))
NIL ; ok
(pathname-version (pathname "dir/"))
NIL ; ok
(pathname-version (pathname "file"))
NIL ; ok

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; should be NIL!
(pathname-version (merge-pathnames "file" "/tmp/"))
:NEWEST ; should be NIL!


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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 16:31

Message:
Unfortunately, there is even more related bugs like this.

(length (directory "/tmp/*/"))
13

(length (directory "/tmp/*"))
7

So my /tmp directory has files and directories too, then:

(pathname-version (car (directory "/tmp/*/")))
NIL ; correct

(pathname-version (car (directory "/tmp/*")))
:NEWEST ; should be NIL!

But the file pathname creation seems to be good

(pathname-version (pathname "does-not-exist.dne"))
NIL


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

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

[ clisp-Bugs-3405120 ] probe-pathname set :newest version

[SourceForge.net <no...@so...>]

Bugs item #3405120, was opened at 2011-09-06 13:12
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3405120&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: Pending
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Gabor Balazs (gabalz)
Assigned to: Sam Steingold (sds)
Summary: probe-pathname set :newest version

Initial Comment:

$ clisp --version
GNU CLISP 2.49 (2010-07-07) (built 3519331083) (memory 3519302729)
Software: GNU C 4.4.5 
gcc -O2 -march=core2 -fomit-frame-pointer -pipe -Wa,--noexecstack -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -I. -Wl,-O1 -Wl,--as-needed  /usr/lib64/libreadline.so -lncurses -ldl /usr/lib64/libavcall.a /usr/lib64/libcallback.a  -L/usr/lib64 -lsigsegv -L/usr/lib64 -lc libgnu_cl.a 
SAFETY=0 TYPECODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY
libsigsegv 2.8
libreadline 6.1
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 WORD-SIZE=64 PC386 UNIX)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: /usr/lib64/clisp-2.49/
User language: ENGLISH
Machine: X86_64 (X86_64) localhost [127.0.0.1]

The problem:

probe-pathname sets the version field to :NEWEST, and so this pathname is never EQUAL to another one returned by PATHNAME.

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; this should be NIL

(equal (probe-pathname "/tmp/") (pathname "/tmp/"))
NIL

Furthermore, MAKE-PATHNAME does not initializes the VERSION slot in the following case:

(defparameter *path* (probe-pathname "/tmp/"))
*PATH*

(pathname-version (make-pathname :version NIL :defaults *path*))
:NEWEST ; this should be NIL

This workaround can be done, but this is ugly:

(pathname-version (make-pathname :version NIL :name (pathname-name *path*) :defaults *path*))
NIL


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

>Comment By: Sam Steingold (sds)
Date: 2011-09-14 09:51

Message:
1. set *parse-namestring-ansi* to T so that symbols are not treated as
pathname designators.
in your case when (probe-pathname "nonexistent") returns NIL,
pathname-version converts it to a pathname with NIL version. see
<http://clisp.org/impnotes/filename-misc.html#parsename>

2. from what I can see, clisp always returns :newest for versions of
truenames. I don't see any problems with that. 

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-13 19:38

Message:
I see your point, but I think there are still problems.

Problem #1:

http://www.lispworks.com/documentation/HyperSpec/Body/f_merge_.htm
The standard says: "If pathname does not specify a name, then the version,
if not provided, will come from default-pathname, just like the other
components."

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; so this should be NIL

as fortunately
(pathname-version "/tmp/")
NIL

Problem #2: 

(pathname-version (probe-pathname "/tmp/file"))
NIL

(pathname-version (probe-pathname "/tmp/dir/"))
NIL

(pathname-version (probe-pathname "/tmp/"))
:NEWEST ; should be NIL

I think CLISP should be consistent here. Why does it return :NEWEST in the
last case?

Problem #3:

(pathname-version (car (directory "/tmp/*/")))
NIL

(pathname-version (car (directory "/tmp/*")))
:NEWEST

Is there any way to let CLISP's directory function return NIL in this last
case?
Otherwise I have to convert all the file pathnames if I want consistency.
Eg, I want to compare pathnames with the equal function.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 18:39

Message:
http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/fun_merge-pathnames.html
default-version---a valid pathname version. The default is :newest

i.e., whenever pathnames are merged without an explicit default-version
argument, 
the result will have the :newest version unless the original pathnames
have non-trivial versions
which is unlikely because no modern filesystem has a notion of a version
built-in.

i.e., the behavior you are complaining about is mandated by the standard.
moreover, it is at least somewhat useful because it lets you know whether
the pathname is a result of a merge with *default-pathname-defaults* or of
raw parsing.


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 18:39

Message:
This bug report is now marked as "pending"/"invalid".
This means that we think that the problem you report is not a problem with
CLISP.
Unless you - the reporter - act within 2 weeks, the bug will be
permanently closed.
Sorry about the inconvenience - we hope your silence means that you agree
that this is not a bug in CLISP.

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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 17:23

Message:
Furthermore,

(pathname-version (pathname "/tmp/"))
NIL ; ok
(pathname-version (pathname "dir/"))
NIL ; ok
(pathname-version (pathname "file"))
NIL ; ok

(pathname-version (merge-pathnames "dir/" "/tmp/"))
:NEWEST ; should be NIL!
(pathname-version (merge-pathnames "file" "/tmp/"))
:NEWEST ; should be NIL!


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

Comment By: Gabor Balazs (gabalz)
Date: 2011-09-11 16:31

Message:
Unfortunately, there is even more related bugs like this.

(length (directory "/tmp/*/"))
13

(length (directory "/tmp/*"))
7

So my /tmp directory has files and directories too, then:

(pathname-version (car (directory "/tmp/*/")))
NIL ; correct

(pathname-version (car (directory "/tmp/*")))
:NEWEST ; should be NIL!

But the file pathname creation seems to be good

(pathname-version (pathname "does-not-exist.dne"))
NIL


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

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

[ clisp-Bugs-3407260 ] linux:tcsetattr fails - ffi problem

[SourceForge.net <no...@so...>]

Bugs item #3407260, was opened at 2011-09-10 13:41
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3407260&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: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Brad Parker (jbparker1)
>Assigned to: Sam Steingold (sds)
Summary: linux:tcsetattr fails - ffi problem

Initial Comment:
I'm using the stock clisp on ubuntu 9.1 (which is admitted, old).
The linux:tcsettattr call fails with an ffi problem.

sorry if this has been fixed.

Welcome to GNU CLISP 2.44.1 (2008-02-23) <http://clisp.cons.org/>

(let* ((descriptor (linux:open "/dev/ttyS0" ;;(device port)
			       (logior linux:O_RDWR linux:O_NDELAY)
			       (logior linux:S_IRUSR linux:S_IWUSR)))
       (attributes (get-attributes descriptor)))
  (linux:tcsetattr descriptor linux:TCSANOW (linux:tcgetattr descriptor)))

*** - FFI::FOREIGN-CALL-OUT: Illegal foreign data type "tcflag_t"


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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 09:23

Message:
thank you for your bug report.
the bug has been fixed in the source tree (mercurial/hg).
you can either wait for the next release (recommended)
or check out the current mercurial tree (see http://clisp.org)
and build CLISP from the sources (be advised that between
releases the source tree is very unstable and may not even build
on your platform).

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

Comment By: Brad Parker (jbparker1)
Date: 2011-09-14 06:11

Message:
Wait.  I am wrong.  my appologies.

linux:tcgetattr returns multiple values.  What you did is correct. 

And it does not seem to fail in the same way running from the top of the
tree.

ok, thanks - I think that answers my question.



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

Comment By: Brad Parker (jbparker1)
Date: 2011-09-14 06:07

Message:
Right.  I see that.  But you're not doing what I did.

linux:txgetattr returns a structure.

linix:tcsetattr takes a structure.

what you did, namely:

Break 1 [4]>
[9]> (linux:tcsetattr 4 linux:TCSANOW (nth-value 1 (linux:tcgetattr 4)))
-1

does not send a structure to linux:tcsetattr.  So, it failed and returned
an error (-1).

I want you to try this:

(linux:tcsetattr 4 linux:TCSANOW  (linux:tcgetattr 4))

Which will send the entire output of tcgetattr to tcsetattr.  That is what
I did and that is what failed.

thanks



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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 00:20

Message:
[1]> (linux:open "/dev/ttyS0" ;;(device port)
                             (logior linux:O_RDWR linux:O_NDELAY)
                             (logior linux:S_IRUSR linux:S_IWUSR)))
4
[2]> (linux:tcgetattr 4)
-1 ;
#S(LINUX:termios :C_IFLAG 0 :C_OFLAG 0 :C_CFLAG 0 :C_LFLAG 0 :C_LINE 0
   :C_CC #(0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0)
   :C_ISPEED 0 :C_OSPEED 0)
[3]> (linux:tcsetattr 4 linux:TCSANOW -1)

*** - FFI::FOREIGN-CALL-OUT: -1 cannot be converted to the foreign type
       #(FFI:C-STRUCT LINUX:termios NIL
         #(LINUX::c_iflag LINUX::c_oflag LINUX::c_cflag LINUX::c_lflag
           LINUX::c_line LINUX::c_cc LINUX::c_ispeed LINUX::c_ospeed)
         #<COMPILED-FUNCTION LINUX:make-termios> #1="tcflag_t" #1# #1#
#1#
         #2="cc_t" #(FFI:C-ARRAY #2# 32) #3="speed_t" #3#)

Break 1 [4]> 
[9]> (linux:tcsetattr 4 linux:TCSANOW (nth-value 1 (linux:tcgetattr 4)))
-1

i.e., I do not get the 'illegal foreign data type" error.

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

Comment By: Brad Parker (jbparker1)
Date: 2011-09-13 20:22

Message:
it's the tcsetattr that is failing;

can you try this:

(linux:tcsetattr descriptor linux:TCSANOW (linux:tcgetattr descriptor))

That is what is failing - it returns "*** - FFI::FOREIGN-CALL-OUT: Illegal
foreign data type "tcflag_t""


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 18:31

Message:
I do not have the "get-attributes" function.
here is what I see with the current hg head:

[1]> (linux:open "/dev/ttyS0" ;;(device port)
                              (logior linux:O_RDWR linux:O_NDELAY)
                              (logior linux:S_IRUSR linux:S_IWUSR)))
4
[2]> (linux:tcgetattr 4)
-1 ;
#S(LINUX:termios :C_IFLAG 0 :C_OFLAG 0 :C_CFLAG 0 :C_LFLAG 0 :C_LINE 0
   :C_CC #(0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0)
   :C_ISPEED 0 :C_OSPEED 0)
[3]> 

is this reasonable?

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

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

[ clisp-Bugs-3407260 ] linux:tcsetattr fails - ffi problem

[SourceForge.net <no...@so...>]

Bugs item #3407260, was opened at 2011-09-10 13:41
Message generated for change (Comment added) made by jbparker1
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3407260&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: Brad Parker (jbparker1)
Assigned to: Bruno Haible (haible)
Summary: linux:tcsetattr fails - ffi problem

Initial Comment:
I'm using the stock clisp on ubuntu 9.1 (which is admitted, old).
The linux:tcsettattr call fails with an ffi problem.

sorry if this has been fixed.

Welcome to GNU CLISP 2.44.1 (2008-02-23) <http://clisp.cons.org/>

(let* ((descriptor (linux:open "/dev/ttyS0" ;;(device port)
			       (logior linux:O_RDWR linux:O_NDELAY)
			       (logior linux:S_IRUSR linux:S_IWUSR)))
       (attributes (get-attributes descriptor)))
  (linux:tcsetattr descriptor linux:TCSANOW (linux:tcgetattr descriptor)))

*** - FFI::FOREIGN-CALL-OUT: Illegal foreign data type "tcflag_t"


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

>Comment By: Brad Parker (jbparker1)
Date: 2011-09-14 06:11

Message:
Wait.  I am wrong.  my appologies.

linux:tcgetattr returns multiple values.  What you did is correct. 

And it does not seem to fail in the same way running from the top of the
tree.

ok, thanks - I think that answers my question.



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

Comment By: Brad Parker (jbparker1)
Date: 2011-09-14 06:07

Message:
Right.  I see that.  But you're not doing what I did.

linux:txgetattr returns a structure.

linix:tcsetattr takes a structure.

what you did, namely:

Break 1 [4]>
[9]> (linux:tcsetattr 4 linux:TCSANOW (nth-value 1 (linux:tcgetattr 4)))
-1

does not send a structure to linux:tcsetattr.  So, it failed and returned
an error (-1).

I want you to try this:

(linux:tcsetattr 4 linux:TCSANOW  (linux:tcgetattr 4))

Which will send the entire output of tcgetattr to tcsetattr.  That is what
I did and that is what failed.

thanks



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

Comment By: Sam Steingold (sds)
Date: 2011-09-14 00:20

Message:
[1]> (linux:open "/dev/ttyS0" ;;(device port)
                             (logior linux:O_RDWR linux:O_NDELAY)
                             (logior linux:S_IRUSR linux:S_IWUSR)))
4
[2]> (linux:tcgetattr 4)
-1 ;
#S(LINUX:termios :C_IFLAG 0 :C_OFLAG 0 :C_CFLAG 0 :C_LFLAG 0 :C_LINE 0
   :C_CC #(0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0)
   :C_ISPEED 0 :C_OSPEED 0)
[3]> (linux:tcsetattr 4 linux:TCSANOW -1)

*** - FFI::FOREIGN-CALL-OUT: -1 cannot be converted to the foreign type
       #(FFI:C-STRUCT LINUX:termios NIL
         #(LINUX::c_iflag LINUX::c_oflag LINUX::c_cflag LINUX::c_lflag
           LINUX::c_line LINUX::c_cc LINUX::c_ispeed LINUX::c_ospeed)
         #<COMPILED-FUNCTION LINUX:make-termios> #1="tcflag_t" #1# #1#
#1#
         #2="cc_t" #(FFI:C-ARRAY #2# 32) #3="speed_t" #3#)

Break 1 [4]> 
[9]> (linux:tcsetattr 4 linux:TCSANOW (nth-value 1 (linux:tcgetattr 4)))
-1

i.e., I do not get the 'illegal foreign data type" error.

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

Comment By: Brad Parker (jbparker1)
Date: 2011-09-13 20:22

Message:
it's the tcsetattr that is failing;

can you try this:

(linux:tcsetattr descriptor linux:TCSANOW (linux:tcgetattr descriptor))

That is what is failing - it returns "*** - FFI::FOREIGN-CALL-OUT: Illegal
foreign data type "tcflag_t""


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

Comment By: Sam Steingold (sds)
Date: 2011-09-13 18:31

Message:
I do not have the "get-attributes" function.
here is what I see with the current hg head:

[1]> (linux:open "/dev/ttyS0" ;;(device port)
                              (logior linux:O_RDWR linux:O_NDELAY)
                              (logior linux:S_IRUSR linux:S_IWUSR)))
4
[2]> (linux:tcgetattr 4)
-1 ;
#S(LINUX:termios :C_IFLAG 0 :C_OFLAG 0 :C_CFLAG 0 :C_LFLAG 0 :C_LINE 0
   :C_CC #(0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0)
   :C_ISPEED 0 :C_OSPEED 0)
[3]> 

is this reasonable?

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

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