Re: next nightly build problem

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

Bruno Haible writes:
 > > Don Cohen wrote:
 > > >I don't even know how to check in lisp what memory model is in use.
 > > It'd be guesswork.
 > 
 > Call (software-version).

not quite, but turned out to be a good hint:

[1]> (software-version)
"GNU C 6.3.1 20161221 (Red Hat 6.3.1-1)"
[2]> (apropos "SOFTWARE")
SOFTWARE-TYPE                              function
SOFTWARE-VERSION                           function

[3]> (software-type)
"gcc -m64 -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wreturn-type -Wmissing-declarations -Wimplicit -Wno-sign-compare -Wno-format-nonliteral -fno-strict-aliasing -ggdb -O0 -DDEBUG_OS_ERROR -DDEBUG_SPVW -DDEBUG_BYTECODE -DSAFETY=3 -DENABLE_UNICODE -DNO_TERMCAP_NCURSES -DDYNAMIC_FFI -DDYNAMIC_MODULES  libgnu.a  -ldl /usr/local/lib/libavcall.a /usr/local/lib/libcallback.a  /usr/local/lib64/libsigsegv.a -lc  
SAFETY=3 TYPECODES WIDE_HARD SPVW_BLOCKS SPVW_PURE SINGLEMAP_MEMORY
libsigsegv 2.10
libffcall 1.13"
[4]>