Robert Bradshaw wrote: > > SAGE does take a very long time to build, especially on slower > hardware. How many hours do you think is has been running? There > could be a circular build issue (especially with such high make > numbers) but I've never encountered it. > > autoconf is run for each of the (dozens) of packages. It would be > nice to somehow share a single run between all the separate packages, > but this hasn't been figured out yet (if you have any ideas, we'd be > happy to hear). Is it doing autoconf on the same file over and over > again? > > > On Jul 14, 2007, at 12:15 PM, Kyle Schalm wrote: > >> yesterday i tried to install sage 2.6 on a friend's machine running >> debian >> 4.0R0 for powerpc. >> there does not appear to be a binary, so i grabbed the source and >> started >> building. i figured it would take a few hours. >> >> i don't know if sage 2.6 is building correctly and just looks like >> it's >> not, or if it's in an infinite loop. for one thing it seems to be >> spending >> all its time in configuring rather than compiling, and for another >> thing >> it seems to be doing the same thing over and over again, as far as >> i can >> tell from the output. and it is taking way longer than i expected >> (overnight and still going). here's an output snippet. (the numbers >> # in >> "make[#]" are lower than they should be because i interrupted the >> build >> and then restarted it. they were in the mid 500s.) >> >> make[3]: Entering directory >> `/usr/local/sage-2.6/spkg/build/python-2.5.1.p3/src' >> make[3]: Warning: File `configure' has modification time 2.2e+06 s >> in the >> future >> /bin/sh ./configure '--prefix=/usr/local/sage-2.6/local' 'CC=gcc' >> 'LDFLAGS=' >> checking MACHDEP... linux2 >> ... (checking about 500 things) >> checking for build directories... done >> configure: creating ./config.status >> config.status: creating Makefile.pre >> config.status: creating Modules/Setup.config >> config.status: creating pyconfig.h >> config.status: pyconfig.h is unchanged >> creating Modules/Setup >> creating Modules/Setup.local >> creating Makefile >> CONFIG_FILES=Makefile.pre CONFIG_HEADERS= /bin/sh config.status >> config.status: creating Makefile.pre >> make -f Makefile.pre Makefile >> make[4]: Entering directory >> `/usr/local/sage-2.6/spkg/build/python-2.5.1.p3/src' >> make[4]: Warning: File `configure' has modification time 2.2e+06 s >> in the >> future
This timestamp problem seems to be the root of your problem. Where is the build directory coming from, i.e. mounted per NFS or somehow else via network? What is the local time? Is it off by roughly 2.2E06 seconds? Make seems to decent recuresively beyond level 10 and that should not happend because there is no such deep recursion in the normal poython build. python should build just fine on PPC Linux, so unless your build environment is FUBAR you might want to check if older versions of python can be build with your toolchain. <SNIP> Cheerrs, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com 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://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
