On Sun, 31 Jan 2010 09:47:00 +0000, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: > The issue reported on sage-support makes me think we should insist that > updates > are performed with the same version of gcc as that which was used to build > gcc > in the first placed. Basically, two people have found > > 1) Install Sage with older gcc. > 2) Install the latest gcc 4.4.3 > 3) Try to update Sage, and it fails > 4) Build Sage from the start, using gcc 4.4.3 and it works. >
Again, that's not what happened (but I guess I didn't explain it properly). Here's the actual run of events: 1) Build sage-4.3.1 with gcc-4.4.2 on Arch Linux; Sage runs fine, passes doctests, etc. Someone else gets the binary and can use it to run Sage 2) Upgrade gcc to gcc-4.4.3 3) Try to run sage, get errors that the original poster listed 4) Rebuild sage-4.3.1 (so the same version) from scratch with gcc-4.4.3, and everything is fine again (for me, but not for the other person who couldn't use my binary because of a cpu flag issue) I guess the moral of the story is that one needs to exercise care when upgrading gcc on one's machine, although I find it strange that this occurred. I'm not claiming that the scenario that you laid out could not occur; I just wanted to clarify what happened in the case in question. Best, Alex -- Alex Ghitza -- Lecturer in Mathematics -- The University of Melbourne -- Australia -- http://www.ms.unimelb.edu.au/~aghitza/ -- 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
