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.
As I said in the previous email, can you tell us more about your
environment? What make are you using, for example? It seems bizarre that
this doesn't work for you...
Rupert
> Quick fix for this is:
>
> --- src/Makefile.am.orig 2013-08-30 03:45:02.000000000 +0000
> +++ src/Makefile.am
> @@ -72,8 +72,8 @@ 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))
> +bd_$(DEFAULTLISP):
> + for d in $(binary_subdirs); do $(MKDIR_P) binary-$(DEFAULT_LISP)$$d; done
>
> ## Some hunks of lisp that get used by more than one implementation
> LOADDEFSYSTEM = (load "$(top_srcdir)/lisp-utils/defsystem.lisp")
-------------- 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/20130904/d9db607c/attachment.pgp>;