Hello Adrien,

Before sending a support request in panic mode, you should first edit your 
post in a text file....and correct it, thinking about what readers will 
understand.

Because you should first explain what you were trying to do, and then 
giving information about how you failed.

If you do not and post "....I am the most unlucky man in the 
world...because the ghost is in the machine..." then you will get only 
compassion in return.

Dima was good because he guessed you are using your own computer (Apple) 
with OSX operating system....Is he guessing right ?

Myself, I guess you wanted to install SAGE 6.9 on your own computer and 
followed   doc.*sage*math.org/pdf/en/installation/installation.pdf   
(google to get it) instructions.

Have you read that file ?

As your log file shows, there are many curious things from the last command 
(start-sage.sh ?) you have run and, hoping you are not fully incompetent in 
UNIX shell commands , you can check :

- edit file  
*/Volumes/sage-6.9-x86_64-Darwin 
1/Sage-6.9.app/Contents/Resources/start-sage.sh*and check that in line 43, 
there is a  file script call spkg/bin/sage-env
If the file was not found by start-sage.sh, then the current working 
directory (given py pwd, pr PWD variable) or the PATH variable (used by 
UNIX to locate scripts and executable files) is wrong at that point

- the script is trying to get a directory name using the UNIX command 
dirname, but failed because its parameters path is wrong (I guess : with 
white space characters in it) :
*usage: dirname path*


*Error: The path to the Sage directory ($SAGE_ROOT) MUST NOT contain 
spaces.*
Setting of SSAGE_ROOT variable by script were wrong before, you can edit 
script, and add one line after dirname line :  echo "SSAGE_ROOT = (" 
$SSAGE_ROOT ")"  to check it

- the script trying to modify a file on a read-only file system :


*IOError: [Errno 30] Read-only file system: 
'/Volumes/sage-6.9-x86_64-Darwin/Sage-6.9.app/Contents/Resources/sage/local/lib/libasan.la
 
<http://libasan.la>'*run a ls -l command, and you will understand why some 
part (directory or file) of path to libasalan.la is read-only.
Updating a library by sage_relocate surprised me a little...but I am newbie 
in SAGE local (own computer) building.
Previous errors could explain it maybe.

I guess you should clean (remove files) what you have done, and start again 
a local build, following the installation pdf.
You need to check environment variables setting (SAGE_ROOT,SSAGE_ROOT and 
so on) either by command lines you typed or in scripts files (edited by you 
or not).


Dominique



-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

Reply via email to