On Wed, Jul 29, 2009 at 1:51 PM, Justin C. Walker<[email protected]> wrote: > > > On Jul 29, 2009, at 06:18 , William Stein wrote: > >> >> On Wed, Jul 29, 2009 at 4:46 AM, Michael >> Brickenstein<[email protected]> wrote: >>> >>> Hi! >>> I have a problem with gdb in sage-4.1.0: >>> Maybe, there is some -arch x86_64 missing. >> >> Interesting. Did you build 64-bit OS X sage yourself? >> >> When I try with a binary, I *don't* get that error, but I do get a >> different error: >> >> sage -gdb >> ... >> >> RuntimeError: unable to determine branch?! >> Error importing ipy_profile_sage - perhaps you should run %upgrade? >> WARNING: Loading of ipy_profile_sage failed. >> sage: >> >> That's a completely different error than you got. This was from a >> binary install of Sage 64-bit. >> >> On the original build machine with the same compiler, etc., "sage >> -gdb" works perfectly. Maybe using "sage -gdb" is very sensitive to >> the XCode compiler version. > > Another observation: > > Using the 64-bit 4.1 binary (Intel, 10.5) from sagemath.org, I install > it, and can run it (getting a "moving...; do not interrupt" message) w/ > o problems. > > When I run "./sage -gdb", it appears to work, but I get ~1400 lines > like this: > > warning: Could not find object file "/Users/was/build/64bit/ > sage-4.1.rc1/spkg/build/pyprocessing-0.52.p0/src/build/ > temp.macosx-10.3-i386-2.6/src/semaphore.o" - no debug information > available for "src/semaphore.c". >
When I see that I think: pyprocessing is replaced by multiprocessing which is included standard in python 2.6, so we can get rid of the pyprocessing spkg completely and thus solve the above problem. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
