Re: [MIT-Scheme-devel] It stopped working..

[Taylor R Campbell]

   Date: Fri, 6 Nov 2009 12:57:43 -0800
   From: Joe Marshall <address@hidden>

   > Did you run `make maintainer-clean' first?

   Hmmm.  Nope.  I'll try it.

It's probably best at this point to try a totally fresh Git clone,
really.  That's what I always do.  I don't use etc/run-three-stages
myself, by the way -- I have a different script that sits outside the
Git repository and runs `git clone' three times.

   Well, I kludged my way around until I got to this point:

   Unhandled signal received.
   Killed by SIGSEGV.
   make[1]: *** [build-bands] Error 1
   make[1]: Leaving directory `/GitRepository/mit-scheme/src'
   make: *** [all-native] Error 2
   # Value: 2

Probably because I changed the calling conventions on x86-64.  These
will be unstable for a little while as I make changes, and you'll need
to rebootstrap afresh from totally clean sources and a LIARC snapshot.
(It can be done by hand without LIARC, but it's long and arduous.)
Whenever I make changes like this I put `*** NOTE:' in the commit
message with a summary of what you need to do to proceed.  I'll say
when I think the calling conventions are stable.

   So now I'm trying to roll back my local tree to three days ago.
   (wish me luck.  Git doesn't seem to have a `pretend the last
   three days never happened' command.)

I tried to figure that out, and the best I could manage was `rm -rf *;
git reset --hard <commit-id>'.  The commit id you probably want is
d9a39924ae7154c0122c901f5ad5c453938fab44, which precedes the rewriting
of the configure scripts.