On Thu, 04 Dec 2014 12:29:03 kcrisman wrote: > On Thursday, December 4, 2014 3:26:09 PM UTC-5, kcrisman wrote: > > > Incidentally, though I don't think I'd want to do this long-term, I > >> > >> think I > >> > >> > might be interested in pulling off one final set of binaries for PPC > >> > >> for > >> > >> > Sage 6.4.1 if it were not too hard to go back to commit 9f3a73e9 in > >> > build/pkgs/gcc/ only - would that screw anything up? > >> > >> I think we did go to 4.9.1 (initially) purely to support yosemite. So I > >> don't > >> think that would break anything. > > > > Yes, that's what I thought. I don't know how much this is integrated into > > other stuff, though. > > > >> gcc 4.0.1 is definitely too old to build 4.9.x. You have need a stepping > >> stone > >> at 4.6 or 4.7 (probably not 4.8). > > > > Okay, that's what I thought. Nuts. > > The problem is one needs a working Sage to get at the fix-spkg-checksums or > whatever it's called, plus to have a working git to revert anything needed > to revert there... sigh. Not today, anyway. Would definitely prepare source on another computer.
Francois -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
