[sage-devel] Re: sage-4.6.1-linux-32bit-fedora_release_13_goddard fails to run

2011-01-15 Thread asd1815
about the naming scheme for Mac OS X where the package was labeled 32-bit and it was only compatible with 64-bits. On Jan 14, 3:53 pm, asd1815 wrote: > I am aware of that's why I pasted it in there. > > Why would you package something and label it with "Fedora13 release&quo

[sage-devel] Re: sage-4.6.1-linux-32bit-fedora_release_13_goddard fails to run

2011-01-14 Thread asd1815
one should put a pre-req section asking for 3.4.14 On Jan 14, 2:15 pm, Dima Pasechnik wrote: > the binary release you are using apparently needs > GLIBCXX_3.4.14, and you have an older version (GLIBCXX_3.4.13) > > On Jan 13, 8:29 pm, asd1815 wrote:> I am running Fedora > 13 wit

[sage-devel] sage-4.6.1-linux-32bit-fedora_release_13_goddard fails to run

2011-01-13 Thread asd1815
information.| -- --- ImportError Traceback (most recent call last) /home/asd1815/Downloads/sage/local/lib/python2.6/site

[sage-devel] Re: Compiling Sage 4.3.1 on Mac OS X 10.6.2 fails

2010-02-05 Thread asd1815
e missed it. > > -M. Hampton > > On Feb 3, 6:53 pm, asd1815 wrote: > > > > > I just tried to compile from source to get a 32-bit version running on > > my laptop. > > > I have: > > > $gcc -v > > Using built-in specs. > > Target: i686-a

[sage-devel] Compiling Sage 4.3.1 on Mac OS X 10.6.2 fails

2010-02-03 Thread asd1815
Error 2 Error building MPIR. real2m9.983s user0m45.948s sys 0m30.516s sage: An error occurred while installing mpir-1.2.2.p0 Please email sage-devel http://groups.google.com/group/sage-devel explaining the problem and send the relevant part of of /Users/asd1815/Downloads/sage-4.3.1/install.log.