By the way, I tried the binary sage-5.0-OSX-64bit-10.6-x86_64-Darwin.dmg
on my Mac Air running OSX 10.6.8, and it crashes on sage: int(2.75) as already reported. Here is the machine data: Model Name: MacBook Air Model Identifier: MacBookAir3,2 Processor Name: Intel Core 2 Duo Processor Speed: 1.86 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache: 6 MB Memory: 4 GB Bus Speed: 1.07 GHz Boot ROM Version: MBA31.0061.B01 SMC Version (system): 1.66f55On Friday, 18 May 2012 00:13:37 UTC+2, Dima Pasechnik wrote: > > OSX 10.6.*-era hardware is weird. Some of it is 32-bit only, some of it > can run both kernels (when you boot you need to press a combination of keys > on the keyboard), some of it is 64-bit. > All of them "can" run 64-bit applications, but I guess this "can" must be > taken with a pinch of salt... > I hate to think what kind of problems might arise if the less capable > hardware is forced to run something > compiled only for more capable one. > > > On Thursday, 17 May 2012 04:44:10 UTC+2, D. S. McNeil wrote: >> >> > Doug, are you using the binary or did you compile your Sage? >> >> Deliberately the binary; I've never had problems with a Sage I've >> successfully compiled myself. [Haven't compiled 5.0 myself yet on >> the Mac, though I did at work today on ubuntu 12.04 and it went fine. >> Will probably try overnight.] >> >> This feels sort of like a 32-bit/64-bit issue, and I'm getting some >> unexpected results in some directions. Trying to remind myself about >> some of the Mac quirks. >> >> FWIW even "sage: 2.3" trips the error for me, so I think pretty much >> every mpfr library call will cause troubles. >> >> >> Doug >> > -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
