[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: set-current-module broken in current Guile CVS version
From: |
thi |
Subject: |
Re: set-current-module broken in current Guile CVS version |
Date: |
Mon, 15 Jan 2001 09:23:49 -0800 |
From: Michael Livshin <address@hidden>
Date: 15 Jan 2001 18:20:26 +0200
Cc: address@hidden, address@hidden, address@hidden
Dirk Herrmann <address@hidden> writes:
> Does the produced file "check-guile" get installed? (please forgive my
> autoconf/make ignorance). If so, is it possible to have it _not_
> installed? IMO, it is sufficient if "make check" works from the build
> directory after "make install" has been performed. This would mean that
> there should not be a need for a check-guile script (or at least that is
> what I think).
not really related, but: it would be nice to have some way to check
the installation, too.
perhaps by having a script that runs the test suite with the installed
guile, or something like that. there wouldn't be any need to install
the script itself, of course.
yeah, check-guile handles this with the "-i INTERPRETER" switch, so that
you can check any guile against the (current build-dir) test-suite. i
just posted a bugfixed version.... try something like:
make
make check
make install
./check-guile -i PREFIX/bin/guile
the auto* tools don't (yet?) support a post-install step, although we
could suggest the above simple check in the INSTALL file for people to
do manually (or add a makefile rule that does it so that people can do
"make post-install-check").
thi