Re: errors when re-compiling CLISP on Slackware

Ive been getting mail delivery errors and then retry errors from
lists.sourceforge.net in relation to the last reply I sent.
I have no idea if anything got through. Below is a copy of what I'd sent
(shown in context I hope). If it messes up the thread I apologise, however
I have no idea why sourceforge's smtp has decided to issue 'temporary'
error messages and bouncing things back when others have been fine.


Below is what I sent :

Hi Sam

On Wed, Feb 14, 2018 at 4:55 PM, Sam Steingold <[email protected]> wrote:

> Hi
>
> > * C Habs <[email protected]> [2018-02-14 15:51:09 +0000]:
> >
> >> You need to fix this.
> >> You should not distribute the ".hg" directory.
> > Well that should be aimed at the Slackware distro maintainers I suspect,
> if
> > ".hg" is indeed distributed.
> > Checking the source file tree, I cannot see a ".hg" directory.
>
> This is weird.
> Could you please take a look at the Makefile in the build directory
> (presumably with-gcc-wall) and see if the "check" target depends on the
> "check-doc" target?
>
>
Sure.

In my current ignorance of the complexity of clisp source tree and build
process files, I opted to run "grep -r check-doc *" on the build directory
as a whole. It yielded:

----
src/ChangeLog:  * makemake.in (check-doc): pass "--tries=1" to wget,
src/ChangeLog:  * makemake.in (check-doc): use IMPNOTES instead of
src/ChangeLog:  (check-doc): use base, not boot, for better symbol coverage
src/ChangeLog:  * makemake.in (check-doc): Use lynx or curl as fallback
when wget
src/ChangeLog:  * makemake.in (check-doc): explicitly check for the
internet connection
src/ChangeLog:  * makemake.in (check-doc): new target to check
Symbol-Table.text
src/makemake.in:    CHECK_DEPS=${CHECK_DEPS}" check-doc"
src/makemake.in:    echol "check-doc: clisp${TEXE} base"
with-gcc-wall/makemake.in:    CHECK_DEPS=${CHECK_DEPS}" check-doc"
with-gcc-wall/makemake.in:    echol "check-doc: clisp${TEXE} base"
with-gcc-wall/makemake:    CHECK_DEPS=${CHECK_DEPS}" check-doc"
with-gcc-wall/makemake:    echol "check-doc: clisp${TEXE} base"
----

You can see there is a reference to "check-doc" in "makemake" under
directrory "with-gcc..." . I checked the "makefile" and all I could spot
relating to a search for "check" & linked to "tests" was:

.
.
.
check-tests : tests lisp.run lispinit.mem
    cd tests && $(MAKE) SHELL='$(SHELL)' LEXE=.run

check-tests-all : tests lisp.run lispinit.mem
    cd tests && $(MAKE) SHELL='$(SHELL)' LEXE=.run clean complete compare

tests :
    -mkdir tests
    cd tests && $(LN_S) ../../tests/Makefile .
    cd tests && $(LN_S) ../../tests/*.lisp .
    cd tests && $(LN_S) ../../tests/*.tst .

# Perform self-tests.
check : check-recompile check-fresh-line check-script check-exec-image
check-tests
.
.
.


I could attach a "clisp.SlackBuild" build log   and the "makefile" (or
anything else) to the next email if that would add any clarity (I'm not
sure it attachments are appropriate or not - please let me know).


> ./configure \
>
[snip]

> > make modular
>
> This looks eminently wrong.
> After "./configure --cbc", you do not need to call _anything_.
> cbc stands for "configure + build + check".
>


I'm not competent to comment on why it is set up like that. Sorry.

As far as I am aware, Slackware endeavour to release the programs just as
the originators/authors intended.

This is a link to the actual Slackware build script should you feel a need
to see it in its entirety:
https://mirrors.slackware.com/slackware/slackware64-14.2/
source/d/clisp/clisp.SlackBuild

I was wondering if the tests are being started from elsewhere in the build
process - there is a 'stream.tst in the "tests" directory - but I guess you
already know about that.

Thank you again for your input so far.

Regards
------------------------------------------------------------------------------
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