Don't compile as root. Chown everything to your normal user, and then do a make distclean && make
On Thursday, August 7, 2014 12:59:12 AM UTC+1, Alasdair wrote: > > I think the trouble may be one which has been reported before: the > permissions in $SAGE_ROOT/local/lib/python/distutils being not group > writable: I'm compiling as root. I went back to $SAGE_ROOT and entered > "chown -R root:root .", and then tried make again - same errors. The > compile gets stuck on pynac. This is the first time (in many many sage > compilations) where I've had an error compiling as root, which leads me to > wonder if either there's some sort of error in the source code, or if > something has been changed so that compiling as root (which I've always > done previously) can't be done. > > Advice is welcome! > > Thanks, > Alasdair > > On Wednesday, 6 August 2014 15:47:39 UTC+10, P Purkayastha wrote: >> >> Try to rebuild the whole thing again, just so as to ensure that >> everything is properly built. >> >> make distclean >> make >> >> On Wednesday, August 6, 2014 12:46:47 PM UTC+8, Alasdair wrote: >>> >>> I'm running Ubuntu 14.04 as a guest VM inside VirtualBox 4.3.12, with >>> Windows 7.1 Enterprise as the host OS. (This gives me access to my >>> university's network, networked printers and drives etc, which are >>> unreachable from linux). And in the middle of compling Sage 6.2 from >>> source, while I was fiddling about with a webcam, the system crashed with >>> the delightful, friendly BSOD. Back in linux, the error messages I >>> received were >>> >>> checking for the distutils Python package... no >>>> configure: error: cannot import Python module "distutils". >>>> Please check your Python installation. The error was: >>>> sys:1: RuntimeWarning: not adding directory '' to sys.path since it's >>>> writable by an untrusted group. >>>> Untrusted users could put files in this directory which might then be >>>> imported by your Python code. As a general precaution from similar >>>> exploits, you should not execute Python code from this directory >>>> make[3]: Entering directory >>>> `/opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2/src' >>>> make[3]: *** No targets specified and no makefile found. Stop. >>>> make[3]: Leaving directory >>>> `/opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2/src' >>>> Error building pynac. >>>> >>>> real 0m1.585s >>>> user 0m0.254s >>>> sys 0m0.159s >>>> ************************************************************************ >>>> Error installing package pynac-0.3.2 >>>> ************************************************************************ >>>> Please email sage-devel (http://groups.google.com/group/sage-devel) >>>> explaining the problem and including the relevant part of the log file >>>> /opt/sage-6.2/logs/pkgs/pynac-0.3.2.log >>>> Describe your computer, operating system, etc. >>>> If you want to try to fix the problem yourself, *don't* just cd to >>>> /opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2 and type 'make' or >>>> whatever is appropriate. >>>> Instead, the following commands setup all environment variables >>>> correctly and load a subshell for you to debug the error: >>>> (cd '/opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2' && >>>> '/opt/sage-6.2/sage' --sh) >>>> When you are done debugging, you can type "exit" to leave the subshell. >>>> ************************************************************************ >>>> make[2]: *** [/opt/sage-6.2/local/var/lib/sage/installed/pynac-0.3.2] >>>> Error 1 >>>> make[2]: Leaving directory `/opt/sage-6.2/build' >>>> make[1]: *** [all] Error 2 >>>> make[1]: Leaving directory `/opt/sage-6.2/build' >>>> >>>> real 0m2.256s >>>> >>> user 0m0.457s >>>> sys 0m0.224s >>>> *************************************************************** >>>> Error building Sage. >>>> >>>> The following package(s) may have failed to build: >>>> >>>> package: pynac-0.3.2 >>>> log file: /opt/sage-6.2/logs/pkgs/pynac-0.3.2.log >>>> build directory: /opt/sage-6.2/local/var/tmp/sage/build/pynac-0.3.2 >>>> >>> >>> >>> I'm not sure if the errors were caused by the system crash, or are the >>> fault of the system itself. But now that I've rebooted - how do I >>> recover? Should I just throw everything away, and start from scratch? >>> >>> Thanks, >>> Alasdair >>> >>> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
