Problems with clisp-2.49.50

Ken Moffat <[email protected]>
Newsgroups gmane.lisp.clisp.devel
Message-ID <[email protected]>
Hi,

sorry this is long, I'm trying to mention what might be important
without having any real clue.

I try to maintain texlive packages for beyond linuxfromscratch
(a "HOWTO" book, if you like) - current versions are in
http://www.linuxfromscratch.org/blfs/view/svn/
specifically clisp-2.49 and libsigsegv-2.11 for xindy-2.5.1. That
combination works fine, except that clisp tests for socket and
streams both segfault so we suppress them.  With that done, xindy
seems to work ok (this is using texlive-2016 from source) and we
have nothing else AFAIK which needs clisp.

Normally I would wait for a new release rather than testing a
development version, particularly for a package such as clisp which
I do not understand (sorry).  But it was mentioned for people doing
preliminary testing for texlive-2017, and some of them have reported
success, so I decided to try it.

Bottom line: when I run either of my xindy tests - source is in
http://www.linuxfromscratch.org/~ken/tex-testfiles/latex-test-20160905.tar.xz
xindy fails to create an index (both tests get the same error) :

for xindynonlua -
 - - -
Loading module
"/opt/texlive/2016/texmf-dist/xindy/modules/base/texindy.xdy"...
Loading module "numeric-sort.xdy"...

Error in line 12:
;; $Id: numeric-sort.xdy,v 1.1 2004/05/24 21:53:27 jschrod Exp $
;;------------------------------------------------------------

;;;
;;; numerically sorting
;;;
;;; "V64" appears before "V128".
;;;

;; FIXME: Works only for up to 7 digits.

(merge-rule "[0-9][0-9][0-9][0-9][0-9][0-9]" "0&" :eregexp)
ERROR: REGEXP:REGEXP-COMPILE: illegal keyword/value pair :EXTENDED,
T in argument list.
The allowed keywords are NIL
system returned with code 256

No file xindynonlua-xindynonlua.ind.
 - - -

Further things which might be relevant:

This is on x86_64.  Our toolchain is using gcc-6.3.0, binutils-2.28,
glibc-2.25.

Because with clisp-2.49 we did not need libffcall, I initially tried
without that. The clisp tests only segfaulted in the streams test.
But xindy failed to work. So I added (static)
libffcall-1.13-20170225 - with that, the socket test too segfaulted.
And xindy still did not work.

Whenever I rebuild clisp, I also rebuild xindy because I'm not clear
how they fit together.

For clisp-2.49.50 I'm passing CPPFLAGS="-DUNIX_BINARY_DISTRIBUTION"
to configure because that was mentioned on tlbuild (xindy errored
without that, so I tried it), but in general I'm using shared system
libs wherever possible, the result is not intended to be
distributed.

After several of those failures I stripped out libffcall, built
clisp-2.49 and rebuilt xindy - that worked fine, so the problem does
appear to be in my build of clisp-2.49.50.

Any suggestions, please ?

ĸen
-- 
`I shall take my mountains', said Lu-Tze. `The climate will be good
for them.'     -- Small Gods

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.