Aleksej Saushev <asau at inbox.ru> writes:
> Rupert Swarbrick <rswarbrick at gmail.com> writes:
>
>> Aleksej Saushev <asau at inbox.ru> writes:
>>> This is a regression since 5.28 (and I think since 5.30):
>>
>> Ah, sorry. One version of your email was missing the quick
>> fix. Unfortunately, that fix is wrong: it is possible to configure
>> Maxima to build with more than one lisp in the same tree.
>
> If the latter is really useful setup (I'd argue it isn't) then the
> following fixes it:
>
>
> --- src/Makefile.am.orig 2013-08-30 03:45:02.000000000 +0000
> +++ src/Makefile.am
> @@ -72,8 +72,10 @@ uninstall-hook: $(WEIRD_UNINSTALL_TARGET
> ## A rule to build binary directories of the form binary-<lispname>
> ## and subdirectories ./numerical and ./numerical/slatec
> binary_subdirs = / /numerical /numerical/slatec
> -bd_%:
> - $(MKDIR_P) $(addprefix $(subst bd_,binary-,$@),$(binary_subdirs))
> +lisps = clisp cmucl scl acl sbcl gcl ecl
> +.PHONY: bd
> +bd:
> + for l in $(lisps); do for d in $(binary_subdirs); do $(MKDIR_P) binary-$$l$$d; done; done
No, the point is that the choice of lisps is made at configure
time. Like
./configure --with-sbcl --with-gcl
Rupert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 315 bytes
Desc: not available
URL: <http://www.math.utexas.edu/pipermail/maxima/attachments/20130905/c7c15c8f/attachment.pgp>;