On May 19, 12:45 pm, Kevin Horton <khorto...@rogers.com> wrote:
> On 19 May 2009, at 11:45, mabshoff wrote:
>
> > On May 19, 6:31 am, Kevin Horton <khorto...@rogers.com> wrote:
> >> As an experiment, I attempted to build sage-4.0.alpha0 on an EeePC
> >> 901
> >> Linux, with the stock Xandros OS. The build failed with:
>
> > Well, if you fiddle with the clock all bets are off. So for starters
> > restart the build with "make" and se if it fails the same time. If it
> > blows up check that the spkg in question is not corrupted. If it isn't
> > send a link to the compressed log as suggested above.
>
> The tarball is corrupted. It worked fine for installs on OS X and a
> Ubuntu VM, but the MD5 changed when I moved it to the EeePC.
Well, that isn't really our fault, is it?
> I'll report success or failure, after I get a good tarball on the EeePC.
>
> This is the second time I've gotten bitten by tarballs with bad MD5s.
> There has got to be a better file format to use - something where the
> archive validity can be checked before launching into a long install.
There is a ticket to add potential corruption detection. See
http://trac.sagemath.org/sage_trac/ticket/329 - patches welcome.
But if you look in the log you ought to see that tar did not unpack
the whole tarball. And if you see any failure while building Sage you
ought to check the md5sum first.
> --
> Kevin Horton
> Ottawa, Canada
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
