Re: errors when re-compiling CLISP on Slackware

Hello again Sam

On Tue, Feb 13, 2018 at 6:15 PM, Sam Steingold <[email protected]> wrote:

> Hi
>
> > * C Habs <[email protected]> [2018-02-13 12:08:26 +0000]:
> >>
> >> You are using unreleased sources from mercurial, right?
> >
> >
> > Probably (actually I do not really know for sure) - the sources are
> > those packaged as part of the Slackware distro install; I guess the
> > source archive would be from mercurial.
>
> 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.

There is a "tests" directory (with make file in it etc).



> >> This failure happens because CLISP does not support https yet.
> >> You can ignore it.
> >
> > How do I ignore it as the slackware build script terminates [and
> > therefore does not produce and installable package] as a result of
> > getting [any] error returned from 'make' I think; is there a configure
> > setting to turn off this testing part to allow the build to complete,
> > or some other approach you could suggest?
>
> The error is in "make check-doc".
> This target is a dependency of "make check" only for developers, i.e.,
> when "test -d .hg" is 0.
> If slackware scripts call "make check-doc" explicitly, this is a bug in
> slackware.
>
>

As far as I can tell from the slackware build script, the "make check-doc"
is not called explicitly (neither is "make check" ).

To me at my level, it seems as if the tests are switched-in as part of the
"configure" settings or something else withing the source tree's build
files.

I removed the tests directory from the source tree and rebuilt just to see
what happened and it failed (as expected) because it could not access the
tests directory during build.

I realise that it might be not convenient to get involved in sorting out a
distro's build process, so I will perhaps go and ask in the slackware
forums and mention what you have said. Just for any lingering interest
however, below are the [pertinent] configure and make calls of the
slackware build script for CLISP.


Thank you for your time and comments.
Best.
Habs.

.
.
.
./configure \
  --prefix=/usr \
  --libdir=/usr/lib${LIBDIRSUFFIX} \
  --mandir=/usr/man \
  --docdir=/usr/doc/clisp-$VERSION \
  --with-module=clx/new-clx \
  --with-module=pcre \
  --with-module=rawsock \
  --with-module=wildcard \
  --with-module=zlib \
  --with-module=fastcgi \
  --cbc with-gcc-wall \
  --with-dynamic-ffi || exit 1
.
.
.
./makemake \
  --with-dynamic-ffi  \
  --prefix=/usr \
  --libdir=/usr/lib${LIBDIRSUFFIX} \
  --with-module=clx/new-clx \
  --with-module=pcre \
  --with-module=rawsock \
  --with-module=wildcard \
  --with-module=zlib \
  --with-module=fastcgi \
  --srcdir=../src \
  > Makefile
make config.lisp
make init
make allc
make $NUMJOBS lisp.run
make interpreted.mem
make halfcompiled.mem
make lispinit.mem
make manual
make modular
.
.
.



Thanks.
>
> --
> Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1561
> http://steingoldpsychology.com http://www.childpsy.net
> http://mideasttruth.com
> http://www.memritv.org http://iris.org.il http://www.dhimmitude.org
> XFM: Exit file manager? [Continue] [Cancel] [Abort]
>
------------------------------------------------------------------------------
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