Re: errors when re-compiling CLISP on Slackware

Hi,

[from Slackware's build:]
> ./makemake \
>   --with-dynamic-ffi  \
[...]
>   > Makefile

To me this looks like the very old recipes. Nowadays, the user typically don't use
makemake themselves, because configure creates the Makefile(s).

> make config.lisp
> make init
> make allc
> make $NUMJOBS lisp.run
> make interpreted.mem
> make halfcompiled.mem
> make lispinit.mem

The use of these many targets  on the part of Slackware was too much IMHO. The Makefile has always
contained enough dependencies to build lispinit.mem after halfcompiled.mem etc.
Maybe this explicit list helped produce logs in more logical order? Or more specific error messages?
 (IMHO, only "make allc" once made sense as an extra early target).
By introducing explicit targets, you introduce dependencies on their names into your build script.

That stuff also seems to predate the "linking sets" (and their required complexity, read
 additional build infrastructure, directory layout etc.).

https://clisp.sourceforge.io/impnotes/modules.html#linkset

If you look carefully into the build process, you'll see that multiple lisp.run and lispinit.mem
are built (in the directories named base, full and others).
Most of these deserve to be tested.

One doesn't start lisp.run -M lispinit.mem -B ... etc. these days.
Instead the docs mention clisp -K full ..., and the clisp wrapper selects one of the lisp.run in the various directories.

>As far as I am aware, Slackware endeavour to release the programs just as the originators/authors intended.
Then switch to the "./configure --cbc" option that Sam talked about (or at least --cb, then run tests separately).

Regarding running tests, you may want to disagree with the amounf of tests that
are performed by the clisp build process and add more of them. Recent postings
and bugs have demonstrated that it's important to run the tests of the individual
 modules as well (if present), not only standard CL compliance tests.

Regards,
	Jörg Höhle

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list