[sage-support] Re: installation problems for Sage binary on Mac

2010-01-24 Thread davidgal...@gmail.com
I downloaded sage-4.3.1-OSX-10.6-i386-Darwin.dmg copied the contents to my disk and tried to execute sage. I received the messages -- | Sage Version 4.3.1, Release Date: 2010-01-20 | | Type notebook() for t

[sage-support] mac G4 dmg file broken

2009-12-28 Thread davidgal...@gmail.com
I downloaded the G4 PowerPC dmg file (all 409 MB) and gried to mount it. Received a message that the file was damaged. Mounted it anyway and tried to copy it to my hard disk. The copy failed. I note that the dmg contained a folder named "sage" rather than the sage.app which appeared on the intel d

[sage-support] Re: Using The VirtualBox Image on Mac OS X

2009-12-14 Thread davidgal...@gmail.com
To add to the mix, I have had no trouble running the virtualbox version of sage on my mac (mini, OS 10.5.8) Dave Galant On Dec 15, 5:40 am, William Stein wrote: > On Mon, Dec 14, 2009 at 1:41 PM, Marshall Hampton wrote: > > I have been unable to get any of the virtualbox sages running on my > >

[sage-support] Re: sage-4.2.1-OSX10.4-32bit-i386-Darwin.dmg

2009-11-18 Thread davidgal...@gmail.com
Ignore! ignore! my bad. brain overload. On Nov 18, 5:57 pm, "davidgal...@gmail.com" wrote: > I downloaded said .dmg file to my iBookG4, copied the sage folder to > my hard disk, opened sage in Terminal and received the message: > > bad CPU type in executable > >

[sage-support] sage-4.2.1-OSX10.4-32bit-i386-Darwin.dmg

2009-11-18 Thread davidgal...@gmail.com
I downloaded said .dmg file to my iBookG4, copied the sage folder to my hard disk, opened sage in Terminal and received the message: bad CPU type in executable ?? David Galant -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this gro

[sage-support] Adventures in sage installation

2009-10-21 Thread davidgal...@gmail.com
A sad tale: Introduction: IBookG4 OSX 10.5.8 PATH = /opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/ Library/Frameworks/Python.framework/Versions/Current/bin:/opt/local/ bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/ sbin:/sbin:/usr/local/bin:/usr/texbin:/

[sage-support] Re: Naming Conventions for Mac PPC binaries

2009-10-14 Thread davidgal...@gmail.com
William Stein: So you can see the root of my confusion. If every build for PPC cpu is 32-bit, why is this mentioned in the name of one build and not the other? > > Regarding 32/64-bit, there has never ever been a 64-bit version of > > Sage on any OS X PPC install. The builds on PPC are all alwa

[sage-support] Naming Conventions for Mac PPC binaries

2009-10-14 Thread davidgal...@gmail.com
I know this is small potatoes, but could you be a bit more clear in the naming conventions for the Mac PPC binaries that you publish (and a blessing upon you for that). There are two binaries named sage-4.1.1-OSX10.4-32bit-G4-PowerMacintosh-Darwin and sage-4.1.1-OSX10.5-PPC-PowerMacintosh-Darwi

[sage-support] Request for help

2009-03-14 Thread davidgal...@gmail.com
When I tried to open sage 3.4 on an iBookG4 (MacOS 10.4.11) I got: Last login: Sat Mar 14 13:34:34 on ttyp1 Welcome to Darwin! iBookG4:~ davidgalant$ /Applications/Analysis/sage/sage -- | Sage Version 3.4, Release Date: 2009-03-1