## #4955 closed defect (duplicate)

# Magma needs write access to $SAGE_ROOT/data/excode/magma

Reported by: | Martin Albrecht | Owned by: | William Stein |
---|---|---|---|

Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |

Component: | interfaces | Keywords: | magma |

Cc: | Merged in: | ||

Authors: | Reviewers: | ||

Report Upstream: | N/A | Work issues: | |

Branch: | Commit: | ||

Dependencies: | Stopgaps: |

### Description

This was on [sage-devel] (2009-01-08):

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/extcodemagma/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/extcodemagma/sage/ basic.lck for writing (Permission deniedIt 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.

### Change History (2)

### comment:1 Changed 14 years ago by

Resolution: | → duplicate |
---|---|

Status: | new → closed |

### comment:2 Changed 14 years ago by

Milestone: | sage-3.4.1 → sage-duplicate/invalid/wontfix |
---|

**Note:**See TracTickets for help on using tickets.

dup of #5041