Dear Mike, dear Stephen, is there be some quick way of solving the problem of having to download the aldor files
https://svn.origo.ethz.ch/algebraist/trunk/aldor/lib/libax0/axiom.as https://svn.origo.ethz.ch/algebraist/trunk/aldor/lib/libax0/axextend.as https://svn.origo.ethz.ch/algebraist/trunk/aldor/lib/libax0/axlit.as https://svn.origo.ethz.ch/algebraist/trunk/aldor/lib/libax0/stub.as https://svn.origo.ethz.ch/algebraist/trunk/aldor/lib/libax0/minimach.as https://svn.origo.ethz.ch/algebraist/trunk/aldor/lib/axllib/src/lang.as at make or configure time or as a separate package in order to build the Aldor-FriCAS interface? Could NAG+aldor.org release them under a license that allows their inclusion into the FriCAS SVN repository and into the distribution of FriCAS (i.e. compatible with the modified BSD license)? That would really help the fricas project. Thank you Ralf On 11/07/2008 04:48 PM, Waldek Hebisch wrote: > Ralf Hemmecke wrote: >> Hello, >> >> here is a patch that should allow to download the aldor interface files >> at configure time. >> >> Please tell me whether you like it or not. If it is OK, I will modify >> src/aldor/Makefile.in to work with that patch, i.e. assume that the >> aldor files are available at build-time. (Note that if configure finds >> out about any missing prerequisite for the aldor interface, then "make" >> will not be run in src/aldor.) >> >> Ralf >> > > I think the patch a few problems: > > 1) Hardcoding MD5 sums in configure. One is not supposed to modify > configure when merely source files are modified. > 2) If there is no md5sum the code would try to download files from > Aldor site even if user has modified files and sums. > 3) We should not try to download Aldor files if user is not going > to build Aldor. > 4) Introducing network delay in configure (normally configure is > quite fast, but in case of problems network operations > > Also, logically it seems better to keep functionality which is > very specific to Aldor (and really not configuring) outside > of configure. > > Now, my preferences would be: > > 1) Make Aldor interface build robustly restartable (so that if some > problem is detected one can just fix the problem and re-run make). > Note: in general our build process should be restartable, but > ATM is not. > 2) Keep handling of Aldor files inside aldor subdirectory. If > desired by Aldor user one can call from configure Aldor specific > script (only if such way turns out to be too clumsy I would > add code directly to configure). > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
