emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Yet another bootstrap failure: Required feature `esh-groups' was not pro


From: Alan Mackenzie
Subject: Yet another bootstrap failure: Required feature `esh-groups' was not provided
Date: Fri, 6 Jun 2008 15:59:15 +0000
User-agent: Mutt/1.5.9i

Hi, Emacs!

Yet another bootstrap failure:

Friday 2006-06-06, ~15:00 UCT
% cvs update
% ./configure --with-gif=no --with-tiff=no
% make bootstrap

.......
.......

Compiling /home/acm/emacs/emacs/lisp/eshell/em-alias.el

In toplevel form:
eshell/em-alias.el:96:1:Error: Required feature `esh-groups' was not provided
make[3]: *** [/home/acm/emacs/emacs/lisp/eshell/em-alias.elc] Error 1
make[3]: Leaving directory `/home/acm/emacs/emacs/lisp'
make[2]: *** [compile] Error 2
make[2]: Leaving directory `/home/acm/emacs/emacs/lisp'
make[1]: *** [bootstrap-build] Error 2
make[1]: Leaving directory `/home/acm/emacs/emacs'
make: *** [bootstrap] Error 2

Am I doing something wrong?

Unless one has the energy to debug build failures, it's hardly worth the
hassle of cvs-updating Emacs at the moment.  It _never_ builds cleanly -
unless the moon is currently blue.  It seems it's not just me.

This constant brokenness of the CVS head saps infinite energy from me.
This probably isn't just me, either.  I really can't be bothered to debug
the latest commission every time I do a CVS update.  And yes, I'm aware
I've broken the CVS build in the past, too.

There was some talk a while ago of commissions triggering an automatic
build.  This would be nice.

A makefile with proper dependencies might also be a solution.

Please can we fix this with some urgency?

-- 
Alan Mackenzie (Nuremberg, Germany).




reply via email to

[Prev in Thread] Current Thread [Next in Thread]