clisp-devel — closed list for developers and testers

Re: Build problem

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

> * Blake McBride <oy...@zp...zr> [2017-03-11 18:48:03 -0600]:
>
> Thanks.  The winning sequence, when the status of the repo is unclear is:
>
> hg pull
> hg update
> ./configure

I suggest that you always pass a build directory to configure:

./configure build-no-options

this way you do `rm -rf build-no-options` instead of `make distclean`.

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 16.10 (yakkety) X 11.0.11804000
http://www.childpsy.net/ http://www.dhimmitude.org http://iris.org.il
http://ffii.org http://palestinefacts.org http://americancensorship.org
Growing Old is Inevitable; Growing Up is Optional.

Re: make check-exec-image failure

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

Hi Bruno,

> * Bruno Haible <oe...@py...t> [2017-03-11 00:54:35 +0100]:
>
>> > My priority for the moment is to fix build errors.
>> 
>> Does this include the "make check-image" failure?
>> https://sourceforge.net/p/clisp/bugs/687/
>
> No. (savemem ... :executable t) is based on
> spvw_memfile.d:savemem_with_runtime, which consists in *appending*
> a memory image to an *executable file*.

I know, I wrote it.

> I certainly won't spend time digging in the internals of the Mach-O
> object format in order to find out how to port this to Mac.

this is a regression on _all_ platforms.

> There is now a general move away from "pack everything into one file"
> to "create separate file for different purposes".

Users, nevertheless, do ask for a "single executable" option.

CLISP, being a developer's tool - as opposed to a user's tool, needs, in
addition to "vendor model" you describe: a team of seasoned
professionals building distributions to be used by many people, a
"custom exec" model, when a lisp hacker throws together a quick solution
and gives is to his 1 or 2 ad hoc users.

E.g., I want to run something on a box in which I cannot install anything.
An executable image - as opposed to two files (runtime + image) - is
easier to distribute.

Thanks.

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 16.10 (yakkety) X 11.0.11804000
http://www.childpsy.net/ http://palestinefacts.org http://honestreporting.com
http://islamexposedonline.com http://www.dhimmitude.org http://ffii.org
A snake who stung your enemy is not necessarily your friend.

Re: Build problem

[Blake M. <bl...@mc...>]

Thanks.  The winning sequence, when the status of the repo is unclear is:

hg pull

hg update

./configure

make distclean

./configure

cd src

make
make check


However, my make check returned:
...
EQL-OK: ERROR
(LET ((V '(A B C)) (VAL '(3 2 1))) (PROGV V VAL (MAPCAR #'EVAL V)))
EQUAL-OK: (3 2 1)
(DEFUN PLUS (&REST ARGS) (APPLY #'+ ARGS))
EQL-OK: PLUS
(FLET ((PLUS (A B) (+ A B)) (MINUS (A B) (- A B))) (LIST (PLUS 1 2) (MINUS
1 2)))
EQUAL-OK: (3 -1)
(LIST (FLET ((PLUS (A B) (- A B))) (PLUS 3 2)) (+ 3 2))
EQUAL-OK: (1 5)
(FLET ((PLUS (A B) (PLUS (PLUS A B A) B))) (PLUS 3 2))
EQL-OK: 10
(LABELS ((QUEUE (L) (IF (CAR L) (QUEUE (CDR L)) 'ENDE))) (QUEUE '(1 2 3)))
EQL-OK: ENDE
(LABELS ((PLUS (A B) (* A (PLUS A A B)))) (PLUS 1 2 3))
[SIMPLE-PROGRAM-ERROR]: EVAL/APPLY: too many arguments given to PLUS

EQL-OK: ERROR
(LET ((A T) (B NIL)) (LIST (IF A 1 2) (IF B 1 2) (IF A 1) (IF B 1)))
EQUAL-OK: (1 2 1 NIL)
(LET ((A T) (B NIL)) (LIST (WHEN A 1 2) (WHEN B 1 2) (WHEN A 1)))
EQUAL-OK: (2 NIL 1)
(LET ((A T) (B NIL)) (LIST (UNLESS A 1 2) (UNLESS B 1 2) (UNLESS A 1)))
EQUAL-OK: (NIL 2 NIL)
(LET ((A T) (B 10) (C NIL)) (LIST (COND (A 1) (T 'END)) (COND (B) (T 'END))
(COND (C 1) (T 'END))))
EQUAL-OK: (1 10 END)
(CASE (+ 1 2) (1 -1) (2 -2) (3 -3))
EQL-OK: -3
(CASE (+ 1 2) (1 -1) (2 -2))
EQL-OK: NIL
(CASE (+ 1 2) ((1 3) -1) (2 -2) (OTHERWISE 100))
EQL-OK: -1
(TYPECASE (+ 1 2) (LIST -2) (NULL -3) (INTEGER -1))
EQL-OK: -1
(BLOCK BLOCKTEST (IF T (RETURN 0)) 1)
[SIMPLE-SOURCE-PROGRAM-ERROR]:
*** - handle_fault error2 ! address = 0xb00000050b0 not in
[0xb0000000000,0xb0000001098) !
SIGSEGV cannot be cured. Fault address = 0xb00000050b0.
GC count: 643
Space collected by GC: 937261960
Run time: 29 716024
Real time: 32 441382
GC time: 4 267826
Permanently allocated: 158648 bytes.
Currently in use: 7982920 bytes.
Free space: 27152 bytes.
make[1]: *** [tests] Segmentation fault
make[1]: Leaving directory `/home/blake/Backup/clisp.hg/src/tests'
make: *** [check-tests] Error 2

Thanks!

Blake


On Fri, Mar 10, 2017 at 8:08 PM, Bruno Haible <br...@cl...> wrote:

> Blake McBride wrote:
> > blake@blake-sony ~/Backup/copy/clisp.hg $ ./configure
>
> Always do "make distclean" before "./configure".
>
> (Or if your copy of clisp was older than 2017-02-19, you need
> to do: "cd src; make distclean".)
>
> Bruno
>
>

Re: next nightly build problem

[Bruno H. <br...@cl...>]

Hi Don,

> Do you think it's adequate to just look for logs that are smaller than
> 3 MB as an indicator of failure, or look at tails of the logs as I now
> do or something else?

The size is not a reliable indicator: I've seen logs that failed, of size > 5 MB
(filled with lots of compiler warnings).

> My normal nightly test creates both a mt and a non-mt clisp and 
> then an ap5 image in each.  Since there is some #+/- mt in the
> current ap5 code, I do want to test each of those, but I don't
> think I have anything that depends on memory models.

Feel free to add such a target in Makefile.devel.

> I see two appearances of multithread in the multi build port list.
> Are those independent of #+MT ?  Using a multi thread gc which is
> independent of #+MT ?  Are any or all of the tests above #+MT ?

It's only testing two different versions of part of the GC algorithm.
One of it is suitable with #+MT, the other is not. But it's not
testing a --with-threads build so far.

Bruno

Re: -Wshift-negative-value

[Bruno H. <br...@cl...>]

Hi Daniel,

> > > > As I said on 2017-02-08, diagnostics from -Wshift-negative-value are
> > > > most probably just noise.
> > >
> > > Why not disable them then?
> >
> > Feel free to do so. Good idea.
> 
> Actually, this is is a very (very) bad idea. Applying a (left) shift to a
> negative value (or shifting by a negative value) is undefined behavior
> since (AFAIK) C99 (which is what we - at least in September - wanted to
> target).
> 
> Quote from (C11) standard (draft) [1]:
> 
> "The result of E1 << E2 is E1 left-shifted E2 bit positions; vacated bits
> are filled with zeros. [..] If E1 has a signed type and nonnegative value
> [..] otherwise, the behavior is undefined."
> N1570 §6.5.7/4

It is undefined because ISO C supports not only two's complement representation
of signed integers, but also one's complement and sign-magnitude. Quote from
[1] § J.3.5:
  "The following are implementation-defined:
   ...
   — Whether signed integer types are represented using sign and magnitude, two’s
     complement, or ones’ complement, and whether the extraordinary value is a trap
     representation or an ordinary value (6.2.6.2)."

But clisp will never support anything else than two's complement arithmetic.
I haven't heard of any machine with one's complement or sign-magnitude in use
since 1980, and even gnulib - which caters to old and traditional systems -
now no longer attempts to support these odd systems [2].

> Thus every single one of those warnings is a possible Heisenbug.
> Any random optimizer pass of any compiler could horribly break our code.

Indeed. In order for this not to happen, I'm adding the gcc option "-fwrapv"
to the CFLAGS.

If, at some point, we want to get rid of this option and let the C compiler
optimize all it can, we'll need to revisit clisp's uses of signed integer
types with the help of -fsanitize=undefined (which is the successor of
the -ftrapv option [3]. -ftrapv does not catch all situations, see attached
file).

Bruno

[1] http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf
[2] http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=67d133ee7b512af59a392f533b17302d71e937db
[3] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68046#c1

Re: -Wshift-negative-value

[Daniel J. <dan...@gm...>]

> > > As I said on 2017-02-08, diagnostics from -Wshift-negative-value are
> > > most probably just noise.
> >
> > Why not disable them then?
>
> Feel free to do so. Good idea.

Actually, this is is a very (very) bad idea. Applying a (left) shift to a
negative value (or shifting by a negative value) is undefined behavior
since (AFAIK) C99 (which is what we - at least in September - wanted to
target).

Quote from (C11) standard (draft) [1]:

"The result of E1 << E2 is E1 left-shifted E2 bit positions; vacated bits
are filled with zeros. [..] If E1 has a signed type and nonnegative value
[..] otherwise, the behavior is undefined."
N1570 §6.5.7/4

Thus every single one of those warnings is a possible Heisenbug.
Any random optimizer pass of any compiler could horribly break our code. We
could force compilation without any optimization to reduce the risk of
hitting such a case, but that's not really reasonable.

[1]: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf

Re: Build problem

[Bruno H. <br...@cl...>]

Blake McBride wrote:
> blake@blake-sony ~/Backup/copy/clisp.hg $ ./configure

Always do "make distclean" before "./configure".

(Or if your copy of clisp was older than 2017-02-19, you need
to do: "cd src; make distclean".)

Bruno

Re: -Wshift-negative-value

[Bruno H. <br...@cl...>]

Hi Sam,

> >> > As I said on 2017-02-08, diagnostics from -Wshift-negative-value are
> >> > most probably just noise.
> >> 
> >> Why not disable them then?
> >
> > Feel free to do so. Good idea.
> 
> Done.

On OpenBSD 6, with gcc 4.2.1, I now get the build error:
cc1: error: unrecognized command line option "-Wno-shift-negative-value"

Please, can you limit the use of this option to the compilers that support it?
Just tried it (I have all gcc releases installed separately): it's supported
starting with gcc 4.4.0, unsupported for older versions.

Using the same idiom that I used to protect the use of -Wno-invalid-offsetof:

    # g++ 3.4 introduced an annoying warning, but has a workaround:
    case "$XCC_GCC_VERSION" in
      2.* | 3.[1-3]*) ;;
      *)
        XCFLAGS=$XCFLAGS' -Wno-invalid-offsetof'
        ;;
    esac

Btw, why did you remove this version check? It is needed:

$ /arch/x86-linux/gnu-inst-gcc/3.4.4/bin/gcc -x c++ -Wno-invalid-offsetof -S hello.c

succeeds but

$ /arch/x86-linux/gnu-inst-gcc/3.3.6/bin/gcc -x c++ -Wno-invalid-offsetof -S hello.c
cc1plus: error: unrecognized option `-Wno-invalid-offsetof'

I tend to assume a gcc version >= 3.1.

Bruno

TEST_NT hack and OpenBSD

[Bruno H. <br...@cl...>]

Hi Sam,

On OpenBSD 7 the usual /usr/bin/make gives a syntax error with
clisp's generated Makefile, on this line:

.SHELL: name=sh path=$(SHELL)

(Syntax error at 'name=sh'.)

This comes from makemake.in:

  # netbsd make ignores the SHELL macro, so we need to use a special
  # target to tell it to respect our shell setting
  # this is important because if configure uses bash and detects TEST_NT=yes,
  # but make uses sh that does not support "test -nt", modules will not build
  case "$host_os" in
    *bsd*) echol '.SHELL: name=sh path=$(SHELL)' ;;
  esac

The comments indicate that this is to make TEST_NT work across different shells.

But

1) 'test file1 -nt -file2' is not standardized by POSIX [1], therefore better
   not rely on it.

2) I don't see anything that uses it.

So I propose to remove this SHELL hack, remove the TEST_NT invocation, and
remove the test.m4 file.

Or, if I overlooked something and it is still needed, limit it to
*freebsd* and *netbsd*.

Bruno

[1] http://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html#tag_20_128

Build problem

[Blake M. <bl...@mc...>]

Hi, Checked out the latest version and having a build problem.  Thought I'd
share:

blake@blake-sony ~/Backup $ uname -a
Linux blake-sony 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
blake@blake-sony ~/Backup $ lsb_release -a
No LSB modules are available.
Distributor ID: LinuxMint
Description: Linux Mint 17.1 Rebecca
Release: 17.1
Codename: rebecca
blake@blake-sony ~/Backup $ gcc --version
gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
blake@blake-sony ~/Backup $ cd copy
blake@blake-sony ~/Backup/copy $ ls -al
total 16
drwxr-xr-x   2 blake blake  4096 Mar 10 19:28 .
drwxr-xr-x 175 blake blake 12288 Mar 10 19:21 ..
blake@blake-sony ~/Backup/copy $ cp -rp ../clisp.hg .
blake@blake-sony ~/Backup/copy $ cd clisp.hg/
blake@blake-sony ~/Backup/copy/clisp.hg $ ./configure
.
.
.
config.status: creating ../Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing po-directories commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
Configure findings:
  FFI:        yes (user requested: default)
  readline:   yes (user requested: default)
  libsigsegv: yes
./makemake --with-dynamic-ffi   > Makefile
make: `config.lisp' is up to date.

To continue building CLISP, the following commands are recommended
  (cf. unix/INSTALL step 4 ff):
    cd src
    vi config.lisp
    make
    make check
blake@blake-sony ~/Backup/copy/clisp.hg $ cd src
blake@blake-sony ~/Backup/copy/clisp.hg/src $ make
.
.
.
configure: ** System Calls (output)
configure: updating cache config.cache
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating link.sh
config.status: creating config.h
config.status: executing depfiles commands
configure: ** System Calls (done)
make[1]: Entering directory `/home/blake/Backup/copy/clisp.hg/src/syscalls'
gcc -I/home/blake/Backup/copy/clisp.hg/src/gllib
-I/home/blake/Backup/copy/clisp.hg/src/gllib -g -O2 -W -Wswitch -Wcomment
-Wpointer-arith -Wreturn-type -Wmissing-declarations -Wimplicit
-Wno-sign-compare -Wno-format-nonliteral -Wno-shift-negative-value -O
-fno-strict-aliasing -DENABLE_UNICODE -DDYNAMIC_FFI -DDYNAMIC_MODULES
 -fPIC -DPIC -I/home/blake/Backup/clisp.hg/src/linkkit \
-c calls.m.c -o calls.o
In file included from
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:25:0:
/home/blake/Backup/copy/clisp.hg/src/gllib/unistd.h:139:3: error: #error
"Please include config.h first."
  #error "Please include config.h first."
   ^
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:219:0,
                 from
/home/blake/Backup/copy/clisp.hg/src/gllib/sys/types.h:28,
                 from /usr/include/stdlib.h:314,
                 from
/home/blake/Backup/copy/clisp.hg/src/gllib/stdlib.h:36,
                 from /home/blake/Backup/clisp.hg/src/linkkit/clisp.h:2070,
                 from
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:20:
/home/blake/Backup/copy/clisp.hg/src/gllib/unistd.h:669:1: error: expected
‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘extern’
 _GL_CXXALIAS_SYS (close, int, (int fd));
 ^
In file included from /usr/include/errno.h:35:0,
                 from
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:29:
/usr/include/x86_64-linux-gnu/bits/errno.h:50:1: error: expected ‘=’, ‘,’,
‘;’, ‘asm’ or ‘__attribute__’ before ‘extern’
 extern int *__errno_location (void) __THROW __attribute__ ((__const__));
 ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘C_subr_posix_stream_lock’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:287:7: warning:
implicit declaration of function ‘__errno_location’
[-Wimplicit-function-declaration]
       && lock_p && (cmd == F_SETLK) && (errno == EACCES || errno ==
EAGAIN))
       ^
In file included from /usr/include/errno.h:35:0,
                 from
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:29:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:287:41: error: invalid
type argument of unary ‘*’ (have ‘int’)
       && lock_p && (cmd == F_SETLK) && (errno == EACCES || errno ==
EAGAIN))
                                         ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:287:60: error: invalid
type argument of unary ‘*’ (have ‘int’)
       && lock_p && (cmd == F_SETLK) && (errno == EACCES || errno ==
EAGAIN))
                                                            ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘C_subr_os_priority’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:906:3: error: invalid
type argument of unary ‘*’ (have ‘int’)
   errno = 0;
   ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:908:15: error: invalid
type argument of unary ‘*’ (have ‘int’)
   failed_p = (errno != 0);
               ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘C_subr_posix_encrypt’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1103:3: error: invalid
type argument of unary ‘*’ (have ‘int’)
   errno = 0; encrypt(block,flag); failed_p = (errno != 0);
   ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1103:47: error:
invalid type argument of unary ‘*’ (have ‘int’)
   errno = 0; encrypt(block,flag); failed_p = (errno != 0);
                                               ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘C_subr_posix_setkey’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1116:3: error: invalid
type argument of unary ‘*’ (have ‘int’)
   errno = 0; setkey(block); failed_p = (errno != 0);
   ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1116:41: error:
invalid type argument of unary ‘*’ (have ‘int’)
   errno = 0; setkey(block); failed_p = (errno != 0);
                                         ^
In file included from /usr/include/netinet/in.h:23:0,
                 from /usr/include/netdb.h:27,
                 from
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1525:
/home/blake/Backup/copy/clisp.hg/src/gllib/sys/socket.h: At top level:
/home/blake/Backup/copy/clisp.hg/src/gllib/sys/socket.h:68:3: error: #error
"Please include config.h first."
  #error "Please include config.h first."
   ^
In file included from /usr/include/x86_64-linux-gnu/sys/types.h:219:0,
                 from
/home/blake/Backup/copy/clisp.hg/src/gllib/sys/types.h:28,
                 from /usr/include/stdlib.h:314,
                 from
/home/blake/Backup/copy/clisp.hg/src/gllib/stdlib.h:36,
                 from /home/blake/Backup/clisp.hg/src/linkkit/clisp.h:2070,
                 from
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:20:
/home/blake/Backup/copy/clisp.hg/src/gllib/sys/socket.h:637:1: error:
expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘extern’
 _GL_CXXALIAS_SYS (socket, int, (int domain, int type, int protocol));
 ^
In file included from /usr/include/netdb.h:27:0,
                 from
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1525:
/usr/include/netinet/in.h:30:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or
‘__attribute__’ before ‘typedef’
 typedef uint32_t in_addr_t;
 ^
/usr/include/netinet/in.h:33:5: error: unknown type name ‘in_addr_t’
     in_addr_t s_addr;
     ^
In file included from
/home/blake/Backup/copy/clisp.hg/src/gllib/arpa/inet.h:46:0,
                 from
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1528:
/usr/include/arpa/inet.h:34:1: error: unknown type name ‘in_addr_t’
 extern in_addr_t inet_addr (const char *__cp) __THROW;
 ^
/usr/include/arpa/inet.h:37:1: error: unknown type name ‘in_addr_t’
 extern in_addr_t inet_lnaof (struct in_addr __in) __THROW;
 ^
/usr/include/arpa/inet.h:41:38: error: unknown type name ‘in_addr_t’
 extern struct in_addr inet_makeaddr (in_addr_t __net, in_addr_t __host)
                                      ^
/usr/include/arpa/inet.h:41:55: error: unknown type name ‘in_addr_t’
 extern struct in_addr inet_makeaddr (in_addr_t __net, in_addr_t __host)
                                                       ^
/usr/include/arpa/inet.h:45:1: error: unknown type name ‘in_addr_t’
 extern in_addr_t inet_netof (struct in_addr __in) __THROW;
 ^
/usr/include/arpa/inet.h:49:1: error: unknown type name ‘in_addr_t’
 extern in_addr_t inet_network (const char *__cp) __THROW;
 ^
/usr/include/arpa/inet.h:77:25: error: unknown type name ‘in_addr_t’
 extern char *inet_neta (in_addr_t __net, char *__buf, size_t __len)
__THROW;
                         ^
In file included from /usr/include/errno.h:35:0,
                 from
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:29:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘C_subr_posix_group_info’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1725:3: error: invalid
type argument of unary ‘*’ (have ‘int’)
   errno = 0;
   ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1736:15: error:
invalid type argument of unary ‘*’ (have ‘int’)
   failed_p = (errno != 0);
               ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘C_subr_posix_user_info’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1800:3: error: invalid
type argument of unary ‘*’ (have ‘int’)
   errno = 0;
   ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1816:15: error:
invalid type argument of unary ‘*’ (have ‘int’)
   failed_p = (errno != 0);
               ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘C_subr_posix__25sethostid’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1920:24: error:
invalid type argument of unary ‘*’ (have ‘int’)
   begin_system_call(); errno = 0; sethostid(hid); e = errno;
end_system_call();
                        ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1920:55: error:
invalid type argument of unary ‘*’ (have ‘int’)
   begin_system_call(); errno = 0; sethostid(hid); e = errno;
end_system_call();
                                                       ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘hardlink_file’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:2889:15: error:
invalid type argument of unary ‘*’ (have ‘int’)
     failed = (errno==ENOENT ? &STACK_3 : &STACK_1);
               ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘symlink_file’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:2917:15: error:
invalid type argument of unary ‘*’ (have ‘int’)
     failed = (errno==ENOENT ? &STACK_3 : &STACK_1);
               ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘C_subr_posix_errno’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:5800:20: error:
invalid type argument of unary ‘*’ (have ‘int’)
       error_code = errno;
                    ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:5812:7: error: invalid
type argument of unary ‘*’ (have ‘int’)
       errno = error_code;
       ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘C_subr_sys_strerror’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:5823:18: error:
invalid type argument of unary ‘*’ (have ‘int’)
     error_code = errno;
                  ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: In function
‘C_subr_posix__25sethostid’:
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c:1920:44: warning:
ignoring return value of ‘sethostid’, declared with attribute
warn_unused_result [-Wunused-result]
   begin_system_call(); errno = 0; sethostid(hid); e = errno;
end_system_call();
                                            ^
/home/blake/Backup/clisp.hg/modules/syscalls/calls.c: At top level:
cc1: warning: unrecognized command line option "-Wno-shift-negative-value"
[enabled by default]
make[1]: *** [calls.o] Error 1
make[1]: Leaving directory `/home/blake/Backup/copy/clisp.hg/src/syscalls'
make: *** [syscalls] Error 2
blake@blake-sony ~/Backup/copy/clisp.hg/src $

Re: make check-exec-image failure

[Bruno H. <br...@cl...>]

Hi Sam,

> > My priority for the moment is to fix build errors.
> 
> Does this include the "make check-image" failure?
> https://sourceforge.net/p/clisp/bugs/687/

No. (savemem ... :executable t) is based on
spvw_memfile.d:savemem_with_runtime, which consists in *appending*
a memory image to an *executable file*.

This is precisely the hack which delayed the port of AKCL to Linux
by 1 year in 1992/1993 (which is why then clisp became more popular
than AKCL on Linux) [1]. I had ported clisp to Linux in 1 day.

And it is because of this lesson that I decided to create 'clisp-link'
based on the notion of a "linking set" [2] where the memory image
is *separate* from the executable.

I certainly won't spend time digging in the internals of the Mach-O
object format in order to find out how to port this to Mac.

Instead, I would better see
  1) the doc clearly state in [3] that this is a platform-dependent
     feature (and list the OSes on which it works),
  2) adjust makemake.in so that this feature gets tested only on
     those platforms where it works.

Additional background:
There is now a general move away from "pack everything into one file"
to "create separate file for different purposes".

* Distros have in fact started to distribute the debug information for binaries
  in separate files. So, instead of having a file 'foo' that may or may not
  contain debug information, you have a file 'foo' without debug information
  and optionally a file '/var/debug/foo' with only the debug information.
  What is the benefit? You can install the debug information on the fly, when
  you need it, for example once the binary crashed for the first time.

* Similarly, in old Windows, executable code and resources were packed in the
  same .exe file. In OS X, which is more modern, the executable code and the
  resources are just normal files in a single 'foo.app' directory.

Bruno

[1] http://www.ibiblio.org/pub/historic-linux/ftp-archives/sunsite.unc.edu/Sep-29-1996/devel/lang/lisp//akcl.README
[2] http://clisp.org/impnotes/modules.html#mod-overview
[3] http://clisp.org/impnotes/image.html

Re: -Wshift-negative-value

[Bruno H. <br...@cl...>]

Hi Sam,

> here is what I see at the tip (./configure --with-debug --cbc on macosx)
> 
> --8<---------------cut here---------------start------------->8---
> Warning: overwriting existing memory mappings in the address range 0x3fffffedd000...0x3fffffeddfff. clisp will likely crash soon!!
> Warning: overwriting existing memory mappings in the address range 0x200262000...0x200262fff. clisp will likely crash soon!!
> Warning: overwriting existing memory mappings in the address range 0x3fffffedc000...0x3fffffedcfff. clisp will likely crash soon!!

Oops. mincore() on Mac OS X is apparently not usable for detecting whether a
page is mapped: it returns 0 in either case. Seen on Mac OS X 10.11 through
the attached program.

Fixed now.

Bruno

Re: -Wshift-negative-value

[Karsten P. <Kar...@gm...>]

On 10.03.17 19:54, Sam Steingold wrote:
> Hi Bruno,
>
>> * Bruno Haible <oe...@py...t> [2017-03-10 19:42:20 +0100]:
>>
>> My priority for the moment is to fix build errors.
>
> Does this include the "make check-image" failure?
> https://sourceforge.net/p/clisp/bugs/687/

Hello,

in my builds make check fails only in make check-exec-image with the 
same message as in the referred bug.

Macos Sierra 10.12.03

[1]> (software-version)
"GNU C 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)"
[2]> (software-type)
"gcc -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wreturn-type 
-Wmissing-declarations -Wimplicit -Wno-sign-compare 
-Wno-format-nonliteral -O -fno-strict-aliasing -DUNIX_BINARY_DISTRIB 
-DENABLE_UNICODE -DDYNAMIC_FFI -DDYNAMIC_MODULES -DNO_GETTEXT  libgnu.a 
-L/usr/local/opt/readline//lib -lreadline -lncurses 
/usr/local//lib/libavcall.a /usr/local//lib/libcallback.a 
/usr/local//lib/libsigsegv.a -lc  -L/usr/X11/lib
SAFETY=0 TYPECODES WIDE_HARD GENERATIONAL_GC SPVW_BLOCKS SPVW_MIXED 
TRIVIALMAP_MEMORY
libsigsegv 2.11
libreadline 7.0
libffcall 1.13"

Anything I can do to help debug this (My lisp is a lot better than my c)?

regards

Karsten

Re: -Wshift-negative-value

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

> * Bruno Haible <oe...@py...t> [2017-03-10 19:42:20 +0100]:
>
>> > As I said on 2017-02-08, diagnostics from -Wshift-negative-value are
>> > most probably just noise.
>> 
>> Why not disable them then?
>
> Feel free to do so. Good idea.

Done.


> My priority for the moment is to fix build errors.

here is what I see at the tip (./configure --with-debug --cbc on macosx)

--8<---------------cut here---------------start------------->8---
Warning: overwriting existing memory mappings in the address range 0x3fffffedd000...0x3fffffeddfff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x200262000...0x200262fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffedc000...0x3fffffedcfff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffedb000...0x3fffffedbfff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffeda000...0x3fffffedafff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x200263000...0x200263fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffed9000...0x3fffffed9fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffed8000...0x3fffffed8fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x200264000...0x200264fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffed7000...0x3fffffed7fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x200265000...0x200265fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffed6000...0x3fffffed6fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffed5000...0x3fffffed5fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffed4000...0x3fffffed4fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x200266000...0x200266fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffed3000...0x3fffffed3fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffed2000...0x3fffffed2fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x200267000...0x200267fff. clisp will likely crash soon!!
Warning: overwriting existing memory mappings in the address range 0x3fffffed1000...0x3fffffed1fff. clisp will likely crash soon!!
--8<---------------cut here---------------end--------------->8---



> Therefore, warnings are lower priority for me, right now.
>
> Bruno
>
>
> ------------------------------------------------------------------------------
> Announcing the Oxford Dictionaries API! The API offers world-renowned
> dictionary content that is easy and intuitive to access. Sign up for an
> account today to start using our lexical data to power your apps and
> projects. Get started today and enter our developer competition.
> http://sdm.link/oxford
> _______________________________________________
> clisp-devel mailing list
> cli...@li...
> https://lists.sourceforge.net/lists/listinfo/clisp-devel
>

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net https://ffii.org
http://americancensorship.org https://jihadwatch.org http://www.dhimmitude.org
Do the arithmetic or be doomed to talk nonsense. --John McCarthy

Re: -Wshift-negative-value

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

Hi Bruno,

> * Bruno Haible <oe...@py...t> [2017-03-10 19:42:20 +0100]:
>
> My priority for the moment is to fix build errors.

Does this include the "make check-image" failure?
https://sourceforge.net/p/clisp/bugs/687/

> Therefore, warnings are lower priority for me, right now.

Noise makes it harder for us to create meaningful reports.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net https://jihadwatch.org
http://think-israel.org http://jij.org http://thereligionofpeace.com
The dark past once was the bright future.

Re: -Wshift-negative-value

[Bruno H. <br...@cl...>]

Hi Sam,

> > As I said on 2017-02-08, diagnostics from -Wshift-negative-value are
> > most probably just noise.
> 
> Why not disable them then?

Feel free to do so. Good idea.

My priority for the moment is to fix build errors.
Therefore, warnings are lower priority for me, right now.

Bruno

Re: build-porting64-gcc-debug_gcsafety

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

Hi Bruno,

> * Bruno Haible <oe...@py...t> [2017-03-10 18:19:40 +0100]:
>
> As I said on 2017-02-08, diagnostics from -Wshift-negative-value are
> most probably just noise.

Why not disable them then?

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net https://jihadwatch.org
http://thereligionofpeace.com http://islamexposedonline.com
Binaries die but source code lives forever.

Re: build-porting64-gcc-debug_gcsafety

[Bruno H. <br...@cl...>]

Hi Sam,

> > * Bruno Haible <oe...@py...t> [2017-03-10 14:37:23 +0100]:
> >
> >> ../src/lispbibl.d:5572:36: warning: left shift of negative value [-Wshift-negative-value]
> >>      objectplus(obj, (soint)(delta) << oint_data_shift)
> >>                                     ^
> 
> shouldn't it be 
> 
>      objectplus(obj, (soint)(delta << oint_data_shift))
> 
> instead?

Definitely no. 'delta' can be a simple 'int' (i.e. 32 bits wide),
and we have configurations with oint_data_shift = oint_addr_shift = 32.

As I said on 2017-02-08, diagnostics from -Wshift-negative-value are
most probably just noise.

Bruno

Re: next nightly build problem

[<Joe...@t-...>]

Hi,

Don Cohen wrote::

>Joe...@t-... writes:
> > The memory models influence some limits, e.g. MOST-POSITIVE-FIXNUM and
> > perhaps ARRAY-TOTAL-SIZE-LIMIT or one of the siblings.
> > Weren't you the one once wondering about the seemingly low
> > string size limit despite a 64 bit build?
>Yes, in fact I found myself wondering about this again just yesterday.
>And now I can't seem to find the answer.  
>What is the reason for this, and where should I have looked for it?

I quickly scanned my archives, didn't find anything about string limits, but found
the following. I've no idea whether Vladimir's observation still applies.

-----Original message-----
Von: Vladimir Tzankov [mailto:vtz...@gm...] 
Gesendet: Mittwoch, 29. Februar 2012 15:38
To: CLisp Development List
Subject: problem with ARRAY-DIMENSION-LIMIT on 64 bit builds with HEAPCODES (e.g. OSX)

On 64 bit OSX clisp uses HEAPCODES and encodes VRECORDs length with 24 bits.
However since it is 64 bit system arraysize_limit_1 is defined as:
((uintV)(vbitm(intLsize)-1)) and ARRAY-DIMENSION-LIMIT is 4294967296.
As a result creating vector with more than 2^24 elements will cause segfault on next garbage collection.
Affected are also large hashtables - they create internally vectors and check sizes directly against "vbitm(oint_data_len)-1" not arraysize_limit_1.

I guess every 64 bit build with HEAPCODES will experience the same problem.

What is the best way to fix this?
-----

Regards,
	Jörg

progress in nightly builds

[<don...@is...>]

Something seems to be fixed in last night's updates - 
my non-MT build seems to have completed for the first time this month.
However the mt build ends with this:

gcc -m64 -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wreturn-type -Wmissing-declarations -Wimplicit -Wno-sign-compare -Wno-format-nonliteral -pthread -fno-strict-aliasing -ggdb -O0 -DDEBUG_OS_ERROR -DDEBUG_SPVW -DDEBUG_BYTECODE -DSAFETY=3 -DENABLE_UNICODE -DMULTITHREAD -DPOSIX_THREADS -DNO_TERMCAP_NCURSES -DDYNAMIC_FFI -DDYNAMIC_MODULES  -Wl,--export-dynamic spvw.o spvwtabf.o spvwtabs.o spvwtabo.o eval.o control.o encoding.o pathname.o stream.o socket.o io.o funarg.o array.o hashtabl.o list.o package.o record.o weak.o sequence.o charstrg.o debug.o error.o misc.o time.o predtype.o symbol.o lisparit.o i18n.o foreign.o unixaux.o zthread.o built.o modules.o libgnu.a  -ldl /usr/local/lib/libavcall.a /usr/local/lib/libcallback.a  /usr/local/lib64/libsigsegv.a -lc  -o lisp.run
./lisp.run -B . -N locale -E UTF-8 -Emisc 1:1 -Epathname 1:1 -norc -m 2MW -lp ../src/ -x '(and (load "../src/init.lisp") (sys::%saveinitmem) (ext::exit)) (ext::exit t)'
Makefile:1425: recipe for target 'interpreted.mem' failed
make: *** [interpreted.mem] Segmentation fault (core dumped)


Any information on diagnosis or prospect of repair is welcome.

Re: build-porting64-gcc-debug_gcsafety

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

Hi Bruno,

> * Bruno Haible <oe...@py...t> [2017-03-10 14:37:23 +0100]:
>
>> ../src/lispbibl.d:5572:36: warning: left shift of negative value [-Wshift-negative-value]
>>      objectplus(obj, (soint)(delta) << oint_data_shift)
>>                                     ^

shouldn't it be 

     objectplus(obj, (soint)(delta << oint_data_shift))

instead?

> So I still cannot guess what produced these "missing intparam.h and
> floatparam.h" errors in your build.

I hope to have time to dig more tomorrow night.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net
http://jij.org https://ffii.org http://no2bds.org http://memri.org
Yellow wine is called "white" because it is made out of green grapes.

Re: build-porting64-gcc-debug_gcsafety

[Bruno H. <br...@cl...>]

Hi Sam,

> okay, build-porting64-gcc-spvw_pure_blocks failed _silently_ (IOW, the
> above command kept going despite the failure).
> The config.log is appended.

This config.log succeeded and produced intparam.h and floatparam.h.

> When I rerun it, it failed with
> 
> --8<---------------cut here---------------start------------->8---
> ../src/lispbibl.d:5572:36: warning: left shift of negative value [-Wshift-negative-value]
>      objectplus(obj, (soint)(delta) << oint_data_shift)
>                                     ^
> ../src/lispbibl.d:501:47: note: in definition of macro ‘designated_init’
>    #define designated_init(field,value) .field=value
>                                                ^~~~~
> ../src/lispbibl.d:3218:35: note: in expansion of macro ‘as_object’
>    #define objectplus(obj,offset)  as_object(as_oint(obj)+(soint)(offset))
>                                    ^~~~~~~~~
> ../src/lispbibl.d:5572:5: note: in expansion of macro ‘objectplus’
>      objectplus(obj, (soint)(delta) << oint_data_shift)
>      ^~~~~~~~~~
> ../src/spvw_weak.d:886:51: note: in expansion of macro ‘fixnum_inc’
>              TheWeakHashedAlist(obj)->whal_count = fixnum_inc(TheWeakHashedAlist(obj)->whal_count,-1);
>                                                    ^~~~~~~~~~
> Makefile:1068: recipe for target 'spvw.o' failed
> make[1]: *** [spvw.o] Error 1
> make[1]: Leaving directory '/home/sds/src/clisp/current/build-porting64-gcc-spvw_pure_blocks'
> --8<---------------cut here---------------end--------------->8---

The 'note' and 'warning' diagnostics are irrelevant for the failure here.

So I still cannot guess what produced these "missing intparam.h and floatparam.h"
errors in your build.

Bruno

Re: ‘rl_readline_state_t’ undeclared

[Bruno H. <br...@cl...>]

Hi Sam,

> > If it's the second case, then why the need to rebuild the *c-ctype-table* from
> > scratch?
> 
> we are not rebuilding it, but rather augmenting it.
> ...
> I think I can fix it.

Nice fix. Well done!

Bruno

clisp-cvs Digest, Vol 75, Issue 2

[<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: Fix build failures with AIX make.
      (cli...@li...)
   2. clisp: Fix build failure on AIX in 64-bit mode.
      (cli...@li...)
   3. clisp: Fix build failure on AIX in 64-bit mode.
      (cli...@li...)
   4. clisp: New heuristic for choosing between TYPECODES and
      HEAPCODES. (cli...@li...)
   5. clisp: clisp.cons.org --> clisp.org
      (cli...@li...)
   6. clisp: Modify the bug#679 fix: defer getting the TRUENAME of
      std... (cli...@li...)
   7. clisp: maint: Add facility for testing builds with
      DEBUG_GCSAFETY. (cli...@li...)
   8. clisp: fix a GC-safety bug in the previous patch
      (cli...@li...)
   9. clisp: (c)year (cli...@li...)
  10. clisp: Fix some gcc warnings about use of fprintf.
      (cli...@li...)
  11. clisp: configure: Fail right away if configure could not
      create ... (cli...@li...)
  12. clisp: Fix build failure with DEBUG_GCSAFETY.
      (cli...@li...)
  13. clisp: asciz_equal: fix comments
      (cli...@li...)
  14. clisp: Wrap atol() and strncmp() in
      begin_system_call/end_system...
      (cli...@li...)
  15. clisp: Add asciz_startswith - a replacement for strncmp not
      requ... (cli...@li...)
  16. clisp: Fix module build failure with inttypes defined in base
      mo... (cli...@li...)


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

Message: 1
Date: Sun, 05 Mar 2017 19:15:54 +0000
From: cli...@li...
Subject: clisp: Fix build failures with AIX make.
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/6af8aa2e07c3
changeset: 15779:6af8aa2e07c37e263cc467607f1e00e06f066887
user:      Bruno Haible <br...@cl...>
date:      2017-03-05 17:03:47 +0100
description:
Fix build failures with AIX make.

diffstat:

 src/ChangeLog   |   6 ++++++
 src/makemake.in |  20 ++++++++++----------
 2 files changed, 16 insertions(+), 10 deletions(-)



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

Message: 2
Date: Sun, 05 Mar 2017 19:15:55 +0000
From: cli...@li...
Subject: clisp: Fix build failure on AIX in 64-bit mode.
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/0fa0cd806c63
changeset: 15780:0fa0cd806c636e34d43baa0d1f07d05171f94e1e
user:      Bruno Haible <br...@cl...>
date:      2017-03-05 19:48:43 +0100
description:
Fix build failure on AIX in 64-bit mode.

diffstat:

 modules/berkeley-db/configure |  152 +++++++++++-------
 modules/fastcgi/configure     |  152 +++++++++++-------
 modules/gdbm/configure        |  152 +++++++++++-------
 modules/libsvm/configure      |  152 +++++++++++-------
 modules/pari/configure        |  152 +++++++++++-------
 modules/pcre/configure        |  152 +++++++++++-------
 modules/postgresql/configure  |  152 +++++++++++-------
 modules/readline/configure    |  152 +++++++++++-------
 modules/zlib/configure        |  152 +++++++++++-------
 src/ChangeLog                 |    6 +
 src/aclocal.m4                |  146 ++++++++++-------
 src/configure                 |  336 +++++++++++++++++++++++------------------
 src/glm4/lib-ld.m4            |  140 ++++++++++-------
 13 files changed, 1209 insertions(+), 787 deletions(-)



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

Message: 3
Date: Sun, 05 Mar 2017 19:15:57 +0000
From: cli...@li...
Subject: clisp: Fix build failure on AIX in 64-bit mode.
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/b64515572c0f
changeset: 15781:b64515572c0fa3c8af863d82a86b48cb50d2d96e
user:      Bruno Haible <br...@cl...>
date:      2017-03-05 19:50:16 +0100
description:
Fix build failure on AIX in 64-bit mode.

diffstat:

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



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

Message: 4
Date: Sun, 05 Mar 2017 19:15:58 +0000
From: cli...@li...
Subject: clisp: New heuristic for choosing between TYPECODES and
	HEAPCODES.
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/6fd1af74ace8
changeset: 15782:6fd1af74ace8416f6a0f868f2ecebcedb3e4a000
user:      Bruno Haible <br...@cl...>
date:      2017-03-05 19:58:30 +0100
description:
New heuristic for choosing between TYPECODES and HEAPCODES.

diffstat:

 src/ChangeLog  |   7 +++++++
 src/lispbibl.d |  39 ++++++++++++++++++++++++++++++++-------
 2 files changed, 39 insertions(+), 7 deletions(-)



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

Message: 5
Date: Tue, 07 Mar 2017 18:27:45 +0000
From: cli...@li...
Subject: clisp: clisp.cons.org --> clisp.org
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/956dc7fbe3bb
changeset: 15783:956dc7fbe3bb30ad6bc264763dca053c20471aca
user:      Sam Steingold <sd...@po...>
date:      2017-03-01 13:23:13 -0500
description:
clisp.cons.org --> clisp.org

diffstat:

 utils/clispload.lisp |  2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)



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

Message: 6
Date: Wed, 08 Mar 2017 18:24:43 +0000
From: cli...@li...
Subject: clisp: Modify the bug#679 fix: defer getting the TRUENAME of
	std...
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/6990cdb9ccb2
changeset: 15784:6990cdb9ccb244176d03084031e8d0f59142dba6
user:      Sam Steingold <sd...@po...>
date:      2017-03-08 13:24:36 -0500
description:
Modify the bug#679 fix: defer getting the TRUENAME of stdio and avoid resolving /proc symlinks to non-existing local files

* src/lispbibl.d (file_stream_truename): Resolve the deferred TRUENAME.
* src/makemake.in (check-script): Add 2 tests.
* src/pathname.d (test_file_stream_named): Check name, not truename.
(file_stream_truename): Move here from src/stream.d
(get_path_info): Do not use local symlinks from "/proc".
(TRUENAME, probe_path_from_stream, DELETE-FILE, RENAME-FILE, OPEN)
(FILE-WRITE-DATE, FILE-AUTHOR): Use file_stream_truename.
* stream.d (handle_pathname): Call PATHNAME instead of TRUENAME.
(handle_to_stream): Do not set strm_file_truename.
* tests/streams.tst, tests/path.tst: Add tests for bug#679.

diffstat:

 src/ChangeLog     |  14 ++++++++++++++
 src/lispbibl.d    |  15 ++++++++-------
 src/makemake.in   |   2 ++
 src/pathname.d    |  49 ++++++++++++++++++++++++++++++++-----------------
 src/stream.d      |  15 ++++-----------
 tests/ChangeLog   |   6 +++++-
 tests/path.tst    |   6 ++++++
 tests/streams.tst |   2 ++
 8 files changed, 73 insertions(+), 36 deletions(-)



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

Message: 7
Date: Thu, 09 Mar 2017 00:56:45 +0000
From: cli...@li...
Subject: clisp: maint: Add facility for testing builds with
	DEBUG_GCSAFETY.
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/948a44cd6e7d
changeset: 15785:948a44cd6e7dbbe9917157c204116cb9f0791b96
user:      Bruno Haible <br...@cl...>
date:      2017-03-09 01:52:58 +0100
description:
maint: Add facility for testing builds with DEBUG_GCSAFETY.

diffstat:

 Makefile.devel |  32 ++++++++++++++++++++++++++++----
 src/ChangeLog  |   6 ++++++
 2 files changed, 34 insertions(+), 4 deletions(-)



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

Message: 8
Date: Thu, 09 Mar 2017 01:47:15 +0000
From: cli...@li...
Subject: clisp: fix a GC-safety bug in the previous patch
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/034bc6d2d51d
changeset: 15786:034bc6d2d51d2641116c187cdaf89f918a48a0ce
user:      Sam Steingold <sd...@po...>
date:      2017-03-08 20:47:07 -0500
description:
fix a GC-safety bug in the previous patch

diffstat:

 src/pathname.d |  2 ++
 1 files changed, 2 insertions(+), 0 deletions(-)



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

Message: 9
Date: Thu, 09 Mar 2017 01:51:37 +0000
From: cli...@li...
Subject: clisp: (c)year
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/d32ccdceae05
changeset: 15787:d32ccdceae054285520bed9395babaabf8d91ff3
user:      Sam Steingold <sd...@po...>
date:      2017-03-08 20:51:33 -0500
description:
(c)year

diffstat:

 src/lispbibl.d |  2 +-
 src/pathname.d |  2 +-
 src/stream.d   |  2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)



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

Message: 10
Date: Thu, 09 Mar 2017 20:44:27 +0000
From: cli...@li...
Subject: clisp: Fix some gcc warnings about use of fprintf.
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/475db05ae2cb
changeset: 15789:475db05ae2cb428151eb4956daf314b38d5a3afe
user:      Bruno Haible <br...@cl...>
date:      2017-03-09 21:41:39 +0100
description:
Fix some gcc warnings about use of fprintf.

diffstat:

 src/ChangeLog      |  17 +++++++++++++++++
 src/errunix.d      |   2 +-
 src/eval.d         |   9 +++++----
 src/predtype.d     |   2 +-
 src/spvw.d         |   4 ++--
 src/spvw_debug.d   |  38 +++++++++++++++++++++-----------------
 src/spvw_memfile.d |   2 +-
 src/spvw_sigsegv.d |   2 +-
 8 files changed, 49 insertions(+), 27 deletions(-)



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

Message: 11
Date: Thu, 09 Mar 2017 20:44:26 +0000
From: cli...@li...
Subject: clisp: configure: Fail right away if configure could not
	create ...
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/c57aa3ea4d4f
changeset: 15788:c57aa3ea4d4f59d065a2f650d714ab335ed32fb6
user:      Bruno Haible <br...@cl...>
date:      2017-03-09 21:32:28 +0100
description:
configure: Fail right away if configure could not create intparam.h.

diffstat:

 configure     |  2 ++
 src/ChangeLog |  6 ++++++
 2 files changed, 8 insertions(+), 0 deletions(-)



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

Message: 12
Date: Thu, 09 Mar 2017 20:44:29 +0000
From: cli...@li...
Subject: clisp: Fix build failure with DEBUG_GCSAFETY.
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/d0fc7df200bf
changeset: 15790:d0fc7df200bfe9c0b70cb829398e9c0e7165f9fa
user:      Bruno Haible <br...@cl...>
date:      2017-03-09 21:43:52 +0100
description:
Fix build failure with DEBUG_GCSAFETY.

diffstat:

 src/ChangeLog  |   6 ++++++
 src/lispbibl.d |  18 ++++++++++++------
 2 files changed, 18 insertions(+), 6 deletions(-)



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

Message: 13
Date: Fri, 10 Mar 2017 02:47:58 +0000
From: cli...@li...
Subject: clisp: asciz_equal: fix comments
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/9af3368b5ab3
changeset: 15791:9af3368b5ab3a5a39ef6a28cb910ab192bb1b07a
user:      Sam Steingold <sd...@po...>
date:      2017-03-09 21:17:57 -0500
description:
asciz_equal: fix comments

diffstat:

 src/lispbibl.d |  8 ++------
 1 files changed, 2 insertions(+), 6 deletions(-)



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

Message: 14
Date: Fri, 10 Mar 2017 02:47:59 +0000
From: cli...@li...
Subject: clisp: Wrap atol() and strncmp() in
	begin_system_call/end_system...
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/eea5838d2ea4
changeset: 15792:eea5838d2ea42d967826a799dcbfc931d4e2e5ed
user:      Sam Steingold <sd...@po...>
date:      2017-03-09 21:24:17 -0500
description:
Wrap atol() and strncmp() in begin_system_call/end_system_call.

* src/misc.d (LISP-IMPLEMENTATION-VERSION): Wrap atol() and strncmp()
in begin_system_call/end_system_call.

diffstat:

 src/ChangeLog |  5 +++++
 src/misc.d    |  2 ++
 2 files changed, 7 insertions(+), 0 deletions(-)



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

Message: 15
Date: Fri, 10 Mar 2017 02:48:00 +0000
From: cli...@li...
Subject: clisp: Add asciz_startswith - a replacement for strncmp not
	requ...
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/9f406724b60b
changeset: 15793:9f406724b60bd2f340916da02c70252105ff5346
user:      Sam Steingold <sd...@po...>
date:      2017-03-09 21:47:51 -0500
description:
Add asciz_startswith - a replacement for strncmp not requiring begin_system_call/end_system_call.

* src/spvw.d (asciz_startswith): Implement.
* src/lispbibl.d (asciz_startswith): Declare.
* src/pathname.d (get_path_info): Use it instead of strncmp().

diffstat:

 src/ChangeLog  |   8 ++++++++
 src/lispbibl.d |  11 +++++++++++
 src/pathname.d |   2 +-
 src/spvw.d     |  16 ++++++++++++++++
 4 files changed, 36 insertions(+), 1 deletions(-)



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

Message: 16
Date: Fri, 10 Mar 2017 03:48:47 +0000
From: cli...@li...
Subject: clisp: Fix module build failure with inttypes defined in base
	mo...
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/47ba0726dfba
changeset: 15794:47ba0726dfbad660234dd6a33ea4c9d2ea659909
user:      Sam Steingold <sd...@po...>
date:      2017-03-09 22:48:41 -0500
description:
Fix module build failure with inttypes defined in base modules.

* src/foreign.d, src/subr.d (PARSE-FOREIGN-INTTYPE): Accept second ERRORP
argument; return 0 when the type is not found and ERRORP is NIL.
* src/foreign1.lisp (parse-c-type): Pass ERRORP=T to PARSE-FOREIGN-INTTYPE.
(finalize-coutput-file): Do not write register_foreign_inttype()
for types already accepted by PARSE-FOREIGN-INTTYPE.

diffstat:

 src/ChangeLog     |   9 +++++++++
 src/foreign.d     |  12 ++++++++----
 src/foreign1.lisp |   5 +++--
 src/subr.d        |   2 +-
 4 files changed, 21 insertions(+), 7 deletions(-)



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

------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford

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

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


End of clisp-cvs Digest, Vol 75, Issue 2
****************************************

Re: ‘rl_readline_state_t’ undeclared

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

Hi Bruno,

> * Bruno Haible <oe...@py...t> [2017-03-08 23:47:43 +0100]:
>
>> The reason is that `(def-c-type foo)` (without definition) modifies
>> *c-type-table* and it becomes a part of CLISP base image (because
>> readline is a base module).
>> Now, when writing the C file after compiling FFI forms, CLISP writes
>> register_foreign_inttype for all such types.
>
> When 'clisp-link' is used to create a linking set B from a linking set A
> and some modules M1, M2, ... [in our case A = base, B = full]: why does
> it need to do anything with the types that are already in *c-type-table*
> of A ?

when compiling linux.lisp, it produces linux.c and writes there all the
C-style (string) types from *c-type-table*.
the assumption has always been that the "canonical" *c-type-table* has
nothing like that.
we need to do it slightly differently; I think I can fix it.

> Or is clisp-link starting out with the memory image from A and adding the
> modules M1, M2, ... to it?

this.

> If it's the second case, then why the need to rebuild the *c-ctype-table* from
> scratch?

we are not rebuilding it, but rather augmenting it.

-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 16.10 (yakkety) X 11.0.11804000
http://www.childpsy.net/ http://thereligionofpeace.com
http://www.memritv.org http://dhimmi.org http://memri.org
Crooks cannot be voted out of power as long as they count the votes.