On Wed, 2001-10-24 at 16:06, Raymond Toy wrote:
> >>>>> "James" == James Amundson <amundson@fnal.gov> writes:
> matlisp bundles a copy of CLOCC defsystem. Since mk:defsystem and
> maxima are "free", it shouldn't be a problem.
Right.
> You just have to
> remember to keep it up-to-date.
Yeah, that's the rub, or at least one of the rubs. I'm still not sure
keeping a private copy the right thing to do.
>> ./configure --use-gcl --use-cmucl --use-clisp --default clisp
>
>
> Isn't this normally done as follows:
>
> mkdir maxima-on-gcl
> cd maxima-on-gcl
> ../configure --use-gcl
> ...
> cd ..
> mkdir maxima-on-cmucl
> cd maxima-on-cmucl
> ../configure --use-cmucl
> ...
That's a good point. I wasn't thinking about that method. It is the
"normal" way. I think the situation here is a little abnormal, however.
I want to make it easy to keep versions for different lisps installed
simultaneously. In the "normal" method, what happens when you type "make
install" in both directories?
> James> I'm happy to do the auto(conf,make) work. It's well within
> James> my expertise. I can't promise to finish it for at least a
> James> month, however. (In Real Life I'm in the process of
>
> You could start with the autoconf file from matlisp as a start. It
> only supports ACL and CMUCL, but it works. It also uses logical
> pathnames to name everything and automatically figures out how to set
> up the translations.
I have not looked at the matlisp packaging, but I will before I go any
further. Thanks for the suggestion.
--Jim