Build failed for intel macbook 10.4.11 Should I post the full log somewhere? Here is the tail:
/Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5 -c sage/misc/darwin_memory_usage.c -o build/temp.macosx-10.3-i386-2.5/sage/misc/darwin_memory_usage.o -w sage/misc/darwin_memory_usage.c:7:32: error: mach/shared_region.h: No such file or directory sage/misc/darwin_memory_usage.c: In function ‘shared_region_size’: sage/misc/darwin_memory_usage.c:34: error: ‘SHARED_REGION_SIZE_PPC’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:34: error: (Each undeclared identifier is reported only once sage/misc/darwin_memory_usage.c:34: error: for each function it appears in.) sage/misc/darwin_memory_usage.c:36: error: ‘SHARED_REGION_SIZE_PPC64’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:38: error: ‘SHARED_REGION_SIZE_I386’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:40: error: ‘SHARED_REGION_SIZE_X86_64’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c: In function ‘in_shared_region’: sage/misc/darwin_memory_usage.c:48: error: ‘SHARED_REGION_BASE_PPC’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:49: error: ‘SHARED_REGION_SIZE_PPC’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:54: error: ‘SHARED_REGION_BASE_PPC64’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:55: error: ‘SHARED_REGION_SIZE_PPC64’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:60: error: ‘SHARED_REGION_BASE_I386’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:61: error: ‘SHARED_REGION_SIZE_I386’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:66: error: ‘SHARED_REGION_BASE_X86_64’ undeclared (first use in this function) sage/misc/darwin_memory_usage.c:67: error: ‘SHARED_REGION_SIZE_X86_64’ undeclared (first use in this function) error: command 'gcc' failed with exit status 1 sage: There was an error installing modified sage library code. On Wed, Jun 24, 2009 at 8:04 AM, Robert Miller <rlmills...@gmail.com> wrote: > > This is the first release of the new cycle, and I've agreed to step in > and co-chair the release with Tom. The source tarball and sage.math > binary are available: > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha0.tar > > http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha0-sage.math-only-x86_64-Linux.tar.gz > > This is the first development release in which the new merge tools > were used by people other than the authors. Several doctests fail on > sage.math: > > sage -t devel/sage-main/sage/graphs/graph.py # 25 doctests > failed > sage -t devel/sage-main/sage/databases/database.py # 20 > doctests failed > sage -t devel/sage-main/sage/geometry/polyhedra.py # 1 > doctests failed > > These are all due to the removal of graph_isom.pyx, and I will be > posting a patch to fix this shortly, at #6394. I think that there was > no way to avoid these failures, since the only way to expose them was > to remove the code, rebuild entirely from scratch, and then run the > tests. > > This release does not include any tickets involving spkg's. I will > make this the main focus of alpha1, which should drop before Friday. > > Each of the following tickets were rejected by the merge scripts, but > unfortunately the failures are not available at this time (this is due > to human error on my part). If you are involved with one of them, you > are encouraged to try applying the patches to 4.1.alpha0 and see why/ > if they failed. Tom and I will eventually do this, but it would be > helpful for people involved in the ticket to get things started: > > 6196 > 5481 > 6276 > 4712 > 5517 > 5991 > 6164 > 6200 > 5902 > 6269 > > Other easy ways to save release managers time, resulting in more > frequent releases and shorter wait times to get your code merged: > > * Please include the trac number in each commit message if possible. > * Please make sure Author and Reviewer fields are set, when changing > the ticket status to "positive review." Since these are used in > generating release notes, please use full names. > * Please adhere to the "trac_####-description.patch" filename format > when creating patch files. > > Cheers, > > Robert Miller (and Tom Boothby) > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
