|
From: | Lennart Borgman (gmail) |
Subject: | Re: Problem with building Emacs diagnosed. Help please! |
Date: | Sat, 09 Aug 2008 01:00:58 +0200 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666 |
Glenn Morris wrote:
Alan Mackenzie wrote:I am not prepared to check out the sources from scratch every time I can't get a build working.I didn't mean that. I meant that you seem at the moment to have gotten into a very weird state somehow, and rather than trying to figure it out, it would be easier to throw it away and start again. If you get into the weird state again, then it makes more sense to investigate it. But for some hopefully transient, never-repeatable glitch, why bother? (Perhaps the "emacs" that your build invokes to make the autoloads is messed up somehow, or it finds the wrong one somehow.) I update and build from CVS every day and almost never see build failures, and they are always rapidly fixed. I'm sure the same is true for others.
I have a problem right now that I hope is solved, but I am not sure. Since I have quite a lot of patches to Emacs I can't just download the sources again. I tried bootstrap-clean, but it did not seem to help. Now I have manually deleted diary-loaddefs.el (or what it was called).
It would be nice if there were a file somewhere in the distribution that explains what to do in strange situations. No need to write it, but every time something stranges pops up and gets solved a note could be added. (Of course the notes must be reviewed now and then to see if they are still valid, but I still think it could save time.)
[Prev in Thread] | Current Thread | [Next in Thread] |