Volker Braun wrote: > KeyboardInterrupt means you pressed Ctrl-C (or maybe your cat ran over > the keyboard)
But it took the cat about half an hour to get bored by "Setting up build directory for gcc-4.9.3.p1" (or probably less, and then a couple of minutes to figure out how to press Ctrl-C, I don't know it). -leif > On Saturday, June 18, 2016 at 2:53:51 AM UTC+2, kcrisman wrote: > > Had to make distclean && make but it had an awful long time setting > up build directory for gcc (prior stuff did fine) and then after > interrupting (after like a half hour), the entire gcc pkg log is: > > Found local metadata for gcc-4.9.3.p1 > > Using cached file > /Users/karl.crisman/Downloads/sage/upstream/gcc-4.9.3.tar.bz2 > > gcc-4.9.3.p1 > > ==================================================== > > Setting up build directory for gcc-4.9.3.p1 > > Traceback (most recent call last): > > File > "/Users/karl.crisman/Downloads/sage/build/bin/sage-uncompress-spkg", > line 246, in <module> > > sys.exit(main()) > > File > "/Users/karl.crisman/Downloads/sage/build/bin/sage-uncompress-spkg", > line 237, in main > > archive.extractall(members=archive.names) > > File > "/Users/karl.crisman/Downloads/sage/build/bin/sage-uncompress-spkg", > line 129, in extractall > > for m in members] > > File > > "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/tarfile.py", > line 1819, in getmember > > tarinfo = self._getmember(name) > > File > > "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/tarfile.py", > line 2395, in _getmember > > member_name = member.name <http://member.name> > > gcc-4.9.3.p1] KeyboardInterrupt > > [gcc-4.9.3.p1] Error: failed to extract > /Users/karl.crisman/Downloads/sage/upstream/gcc-4.9.3.tar.bz2] > > > While doing this, I get process like > > > Load Avg: 1.34, 1.55, 1.66 CPU usage: 29.48% user, 2.94% sys, > 67.56% idle > > 91862 Python 98.1 00:27.40 1/1 0 15 201M+ 0B 0B > 91747 > > > This process is sage-uncompress-spkg > > > This is on El Capitan OS X 10.11.5. Any ideas? I don't think it > should take that long just to extract it? (I'm reluctant to clone > from scratch because I have a number of branches already existing, > though perhaps they are all also pushed to trac, I don't remember.) -- You received this message because you are subscribed to the Google Groups "sage-release" 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 https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
