On Thu, Jan 8, 2009 at 5:48 AM, Martin Albrecht <[email protected]> wrote: > >> RuntimeError: While attempting to compile /usr/local/sage-3.2.3/data/ >> extcode//magma/latex/latex.m (Data file non-existent): >> Can't open lock file /usr/local/sage-3.2.3/data/extcode//magma/latex/ >> latex.lck for writing (Permission denied) >> >> While attempting to compile /usr/local/sage-3.2.3/data/extcode//magma/ >> sage/basic.m (Data file non-existent): >> Can't open lock file /usr/local/sage-3.2.3/data/extcode//magma/sage/ >> basic.lck for writing (Permission denied > > It seems like you need write access to extcode (see above) at least for the > first time you're running Magma from Sage. IIRC there was some talk about > lifting this requirement somehow.
The only idea I have to deal with this is to copy all of extcode/magma into .sage/extcode/magma say, and then have sage only use magma code that's in .sage/extcode/magma/. Whenever sage is upgraded, the .sage/extcode/magma would have to get deleted and re-copied, using a facility similar to how the Gap workspace always gets updated when Sage has been upgraded. Thoughts? William --~--~---------~--~----~------------~-------~--~----~ 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/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
