> You shouldn't have to move it anywhere; Sage doesn't have to live > anyplace in particular. Is it only after you move it that you > encounter problems? Maybe you have permission issues there?
Yes, the problems were only with R packages and only after I moved entire sage folder. I did not want it into my temporary downloads location... The problem was with hard-coded paths, not the permissions. Anyway, the fix was easy. I opened all the files listed above by George: sage/local/lib/R/bin/R sage/local/lib/R/bin/libtool sage/local/lib/R/etc/Makeconf sage/local/lib/R/etc/ldpath sage/local/lib/R/etc/Renviron sage/local/bin/R and edited obvious lines containing hardcoded paths (using find- replace-all at once). I think it is relatively easy for general distribution of Sage compiled for Mac write a post-installation script fixing these lines, in assumption that final destination will be of / Applications/Sage.app type. > No, because there is no such folder by default - I doubt that many Mac > users would even know what /usr/local is, for instance. Agree, but I have more Linux experience, than Mac. I just started to work with Mac and do not know how to convert compiled program into proper .app application, therefore /usr/local/ was a prefered option for me. K. -- 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 URL: http://www.sagemath.org
