> Sage (6.4.1) notebook build failed on 32 bit CentOS 5.11. Version of > sagenb was 0.11.1. To reproduce, build Sage from source (e.g., ./make from > Sage installation directory). CPU was "CPU1: Intel(R) Core(TM)2 Duo CPU > E4400 @ 2.00GHz stepping 0d" per dmesg. Sage runs, but ptest or building > pdf docs replays the error messages, as shown below. The tar file for > sagenb could be unpacked manually OK (in off-tree location). Checksums on > Sage source download tarball matched up OK. What is the best course of > action to get this to build properly? Is there a reason why it failed? > I previously posted a similar item, but it did not appear in the > sage-support list of items, so I am trying it again. > > I wonder if it's because of the bsd tar I used to tar it (I built that package, and have a Mac, and this has been known to cause occasional warning messages, though I don't know about build errors). See e.g. http://superuser.com/questions/318809/linux-os-x-tar-incompatibility-tarballs-created-on-os-x-give-errors-when-unt
What you could do is to retar the directory yourself, and replace the old tar file with that one; then things should work fine. The old release scripts repackaged all our spkg files anyway, but I think the new layout release style does not do that, as it takes tar balls directly from upstream. In this case, an upstream who uses Mac :( -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
