On Sat, Dec 03, 2011 at 06:37:41PM -0800, Jonathan Bober wrote:
> I'm not really sure. I'm hoping that someone else might have some more
> advice. It would be easier to diagnose these failures if they could be
> replicated.
> 
> Some other thoughts: More information about your machine might be useful,
> like the output from 'cat /proc/cpuinfo', and the amount of ram + swap that
> you have. 

My proc info on the Thinkpad T40 is:

processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 9
model name      : Intel(R) Pentium(R) M processor 1500MHz
stepping        : 5
cpu MHz         : 600.000
cache size      : 1024 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr mce cx8 mtrr pge mca cmov clflush dts 
acpi mmx fxsr sse sse2 tm pbe up bts est tm2
bogomips        : 1196.11
clflush size    : 64
cache_alignment : 64
address sizes   : 32 bits physical, 32 bits virtual
power management:

The other thing that might be special is that this laptop has an OS
that has been continually updated since at least Jaunty, if not earlier;
the same disk has moved from one Thinkpad model to the next: T20,T23,T41.

So my system has a lot of history. It even once had Sage installed
and working from Debian packages, but I had to remove it due to lack 
of space. I recently repartitioned to get breathing room in sys, so 
that is why I am trying to install it again.

> Maybe the machine is running out of memory during the build and
> giving a strange error? Maybe you're having actually hardware failures? (If
> you try to build again, does it always fail in the same spot?)

The failures are replicable. However, since I have been just re-running
the make on the same directory for some time, I will, just for tidiness,
create a new fresh build directory, install the two packages there, and
run a make on that.

Dima helped me make some progress; I added the readline-6.2.p2.spkg which
got me past the first tranch of problems; then I applied your suggestion
and added ecl-11.1.2.cvs20111120.p0.spkg.

> It also might be useful for someone else to see your install.log, if you
> send it to me I'll put it somewhere public if you don't mind, or maybe Dima
> can do that. (The missing files don't appear to be part of the maxima spkg
> before it is built, so if it is giving a missing file error, then maybe
> there was some earlier error?)

I will send you the current install.log now however, so you do not have
to wait for 5-6 hours for the de novo build to occur.

> (You might also check the md5 sum of your source download, and make sure
> that nothing went wrong there.)

The md5sum for my tar here:

        b3073997e6c7ec00a269f84ff2e54973  sage-4.7.2.tar

which matches up with the one on the webpage:

        b3073997e6c7ec00a269f84ff2e54973 

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Reply via email to