But anyway, I also should have added something like lmfdb@lmfdb3:~$ lsb_release LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch lmfdb@lmfdb3:~$ lsb_release -a LSB Version: :base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Distributor ID: Scientific Description: Scientific Linux release 6.5 (Carbon) Release: 6.5 Codename: Carbon
lmfdb@lmfdb3:~$ uname -a Linux lmfdb3.maths.bris.ac.uk 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 20:37:17 CST 2013 x86_64 x86_64 x86_64 GNU/Linux On Thu, Mar 13, 2014 at 1:56 PM, Jonathan Bober <[email protected]> wrote: > I do have /dev/stdout. The error message is correct, however. /dev/stdout > is not a directory. (I have no idea why it wants it to be a directory.) > > > On Thu, Mar 13, 2014 at 1:40 PM, Volker Braun <[email protected]>wrote: > >> Why don't you have /dev/stdout? Which operating system? Its supposed to >> be present in Linux, though not POSXI. >> >> >> On Wednesday, March 12, 2014 9:19:46 PM UTC-4, Jonathan Bober wrote: >> >>> I built, and all tests passed. However, I can't seen to install packages: >>> >>> jb12407@lmfdb5:~/sage-6.2.beta4$ ./sage -i gap_packages >>> Found local metadata for gap_packages-4.7.4 >>> Attempting to download package gap_packages-4.7.4 >>> >>> Trying to download http://www.sagemath.org/packages/upstream/gap_ >>> packages/gap_packages-4.7.4.tar.bz2 >>> [Traceback (most recent call last): >>> File "<stdin>", line 35, in <module> >>> File "/data/home/jb12407/sage-6.2.beta4/local/lib/python/urllib.py", >>> line 244, in retrieve >>> tfp = open(filename, 'wb') >>> IOError: [Errno 20] Not a directory: '/dev/stdout' >>> Error: failed to download package gap_packages-4.7.4 >>> jb12407@lmfdb5:~/sage-6.2.beta4$ >>> >>> This might not be beta4, specific. I was seeing it with beta3 and then >>> tried beta4 to see if that was any better, and it wasn't. Has this been >>> seen before? (Maybe I should be sending this straight to trac/sage-devel.) >>> >>> >>> On Wed, Mar 12, 2014 at 5:08 PM, Dima Pasechnik <[email protected]>wrote: >>> >>>> On 2014-03-12, Dima Pasechnik <[email protected]> wrote: >>>> > I cannot seem to be able to build on OSX 10.6.8 and the >>>> > usual Sage-supplied gcc even if I do >>>> > make distclean first. It gets stuck at Singular: >>>> oops, sorry for noise - wrong PATH, wrong libtool... >>>> Please ignore the previous message. >>>> >>>> >>>> -- >>>> 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 http://groups.google.com/group/sage-release. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> 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 http://groups.google.com/group/sage-release. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
