From: Alan Mackenzie <acm@muc.de>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Problem with building Emacs diagnosed. Help please!
Date: Mon, 4 Aug 2008 17:05:17 +0000 [thread overview]
Message-ID: <20080804170517.GA17959@muc.de> (raw)
In-Reply-To: <01ljze53ie.fsf@fencepost.gnu.org>
Hi, Glenn,
On Sun, Aug 03, 2008 at 02:59:05PM -0400, Glenn Morris wrote:
> Alan Mackenzie wrote:
> > As I've said once or twice recently, whilst 'make bootstrap'ping, I've
> > been getting the error message
> Has anyone else seen this? Do you see it in a fresh checkout?
A fresh checkout builds "OK", for the following value of "OK": After
doing ./configure and make bootstrap, the build crashes with
(presumably) a segmentation fault (it said "error 6", or something
similar). After doing "make" ~10 times, emacs was built. At each
attempt, it crashed with a seg fault. I think there's a memory leak
here, but I've said that already.
> It works for me, and I don't see that there is anything wrong here.
> Sorry you're having problems.
Thanks!
> > Loading loaddefs.el (source)...
> > Symbol's function definition is void: eshell-defgroup
> eshell-defgroup does not appear in my loaddefs.el.
It doesn't appear in my new-checkout build, but it does in my usual
Emacs-23, in respect of files
em-{alias,banner,basic,cmpl,dirs,glob,hist,ls,pred,prompt,rebind,script,smart,term,unix,xtra}.el.
In fact, that's pretty much every lisp file which has ;;;###autoloads.
Somehow, autoload.el is failing to redirect the autoloads to the correct
output file (here, eshell/esh-groups.el).
[ ..... ]
> > , i.e. the problem is that `eshell-defgroup' is defined after it is used.
> eshell-defgroup is not autoloaded. It is defined in eshell.el, which
> all the files that use it require. The above line you quote should not
> be in any generated file, not is it for me. I think your build is
> messed up.
Apologies. I inserted ";;;###autoload" on eshell-defgroup myself, in an
attempt to get things working, then forgot about it and got thoroughly
confused.
> > Glenn, when you changed the eshell source to use `eshell-defgroup'
> > instead of just plain old `defgroup' (to which it is aliased anyway)
> > on 21st May 2008, was there some overwhelmingly important reason?
> ... when I made the change for a reason, yes. To replace homegrown
> eshell code with the normal autoload mechanism. Autoload treats
> defgroup specially, eshell needs the whole definition in esh-groups,
> hence the alias subterfuge. I believe it works fine.
Ah, right, I see.
> I think your build tree is messed up somehow.
> I think you have misdiagnosed the problem. Any problem that might
> exist must be due to the build not starting from a clean state for
> some reason.
Yes. But I'm so sick and fed up of not being able to build routinely, I
am going to track down this problem even if it takes me weeks to do it.
I am not prepared to check out the sources from scratch every time I
can't get a build working.
Refactoring autoload.el might be a good first move.
> Sorry, I'm on vacation and it's hard for me to investigate.
Thanks for taking the time to put me right! I hope you're enjoying it!
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2008-08-04 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 10:12 Problem with building Emacs diagnosed. Help please! Alan Mackenzie
2008-08-03 18:13 ` Stefan Monnier
2008-08-03 18:59 ` Glenn Morris
2008-08-03 22:01 ` Glenn Morris
2008-08-04 17:05 ` Alan Mackenzie [this message]
2008-08-04 18:45 ` Chong Yidong
2008-08-04 19:19 ` Alan Mackenzie
2008-08-08 22:53 ` Glenn Morris
2008-08-08 23:00 ` Lennart Borgman (gmail)
2008-08-11 19:18 ` Alan Mackenzie
2008-08-11 19:30 ` Lennart Borgman (gmail)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080804170517.GA17959@muc.de \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.