> So what I would like to do in produce an update to the Sage > 'fricas-1.0.3.spkg' optional package to include building the Aldor > interface if Aldor is present.
Just a comment an no code... if with every FriCAS distribution x.y.z there is a fricas-x.y.z.spkg, I don't see a problem with just including libaxiom.al into that spkg. The .ao files in the .al library are machine independent. There are only the files that are generated into the src/aldor/lib directory that need a build from source. But these are only 8 small files. So the time should be less than a minute. > The build time for the Aldor interface will be an issue unless we can > find a way to do something similar for it. I know that Aldor is able > to generate high-level architecture-independent intermediate code and > even Lisp code, but I am not sure if the make scripts written by Ralf > make caching of this intermediate code or Lisp possible. Building the > Aldor interface currently takes about 30 minutes. We know that this > can be reduced at the expense of a larger library file by optimizing > the use of 'ar'. (Maybe this is due to a bug in 'ar'? Or is it a > problem in the way we are using 'ar'?) The Aldor compiler includes more symbols into the .ao file if it incrementally builds libaxiom.al. I have no idea why it is including that needless information. Sorry, no code, because I am just catching up after vacation and I haven't really looked into fricas-1.0.3.spkg. A link to it would be helpful. Ralf --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "FriCAS - computer algebra system" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/fricas-devel?hl=en -~----------~----~----~----~------~----~------~--~---
