On 1/3/07, Raymond Toy <raymond.toy at ericsson.com> wrote:
> Robert> But even better would be to put them in src/lapack and compile
> Robert> them at the same time as everything else, but just omit them from
> Robert> the final image. Then load(lapack) would just load the lapack binaries
> Robert> instead of compiling them.
>
> I don't know how to do that. Maxima's build system for src is a bit
> messy. The defsystem file compiles and loads everything. Then it's
> done again, using the same defsystem to load everything. Hence,
> everything gets loaded. We'd have to rearrange the defsystem and
> build scripts.
OK, let's not mess with the src build system. Let's put it in
share/lapack. Can we compile it there so that users don't need to?
> We could set *compile-verbose* and friends not to display these
> progress messages. However, on my ppc system it takes a long time
> (15+ minutes?) to compile, so having some messages go by gives the
> user a nice warm fuzzy that something is actually happening.
15 minutes?! I think users are going to be unhappy about that.
I know I will be.
> But there's a precedent for this. affine compiles it's code too, so
> it wouldn't work on read-only file systems either.
I don't want to use affine as a model for other packages.
It is unfortunately something of a mess, from what I can tell.
Thanks for working on this problem --
Robert