Maybe it is my fault. :-( Reading now the script in OpenAxiom, I see that it sets the AXIOM variable like Gaby explained. However, this script cannot run in Windows.
In both installers, I use the AXIOMsys executable, following the previous installer method. If anybody has a suggestion of how I can handle this, please let me know. I apologize for any new friction I had introduced with this. Regards, Alfredo On 9/30/07, root <[EMAIL PROTECTED]> wrote: > Alfredo, > > >| Ah, Gaby, while I've got your attention.... > >| > >| It appears that installing OpenAxiom interferes with an already > >| installed Axiom. > > > >OpenAxiom installs its binaries in a directory distinct from > >any other Axiom flavors. It sets its internal variable AXIOM *within* > >its own script and does not depend on external setting of it. > >The fact that Axiom seems to need external setting of the AXIOM > >environment variable sounds to be like a bug that should be fixed in Axiom. > > We observed that installing OpenAxiom breaks an existing Axiom install. > According to the above it appears that the AXIOM shell variable collision > is not the problem. Can you try it again and see if you can figure out > where the collision occurs? There is no technical reason why the two > projects cannot coexist on the same machine. > > Tim > > _______________________________________________ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer
