From: Dan Nicolaescu <dann@ics.uci.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: Re: Yet another bootstrap failure: Required feature `esh-groups' was not provided
Date: Fri, 06 Jun 2008 11:23:01 -0700 [thread overview]
Message-ID: <200806061823.m56IN1eY005996@sallyv1.ics.uci.edu> (raw)
In-Reply-To: <ejtzg6mqbi.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 06 Jun 2008 13:22:09 -0400")
Glenn Morris <rgm@gnu.org> writes:
> Alan Mackenzie wrote:
>
> > eshell/em-alias.el:96:1:Error: Required feature `esh-groups' was not provided
> [...]
> > Am I doing something wrong?
>
> Yes. Please read INSTALL.CVS, or search the list archives.
>
> (make autogen-clean; make autoloads _may_ help you in this case)
>
> > This constant brokenness of the CVS head saps infinite energy from me.
>
> The constant reporting of the same non-bugs saps my energy (but
> fortunately not an "infinite" amount).
Given that people seem to expect that "make bootstrap" works all the
time, would it be a good idea to make "make bootstrap" to first clean
everything first so that it starts from a clean slate and then it has a
greater chance of meeting people's expectations?
This might reduce the amount of time you have to spend responding to
these types of messages...
next prev parent reply other threads:[~2008-06-06 18:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 15:59 Yet another bootstrap failure: Required feature `esh-groups' was not provided Alan Mackenzie
2008-06-06 17:22 ` Glenn Morris
2008-06-06 18:23 ` Dan Nicolaescu [this message]
2008-06-06 19:27 ` Stefan Monnier
2008-06-06 20:35 ` Alan Mackenzie
2008-06-06 20:41 ` Eli Zaretskii
2008-06-07 2:53 ` Glenn Morris
2008-06-07 9:07 ` Alan Mackenzie
2008-06-07 19:49 ` Glenn Morris
2008-06-07 9:50 ` Alan Mackenzie
2008-06-07 12:19 ` Eli Zaretskii
2008-06-07 20:08 ` Alan Mackenzie
2008-06-07 22:17 ` Stephen J. Turnbull
2008-06-07 22:29 ` Romain Francoise
2008-06-08 2:58 ` Stefan Monnier
2008-06-08 2:56 ` Build-time dependencies Stefan Monnier
2008-06-08 19:03 ` Glenn Morris
2008-06-08 19:25 ` Eli Zaretskii
2008-06-08 19:31 ` David Kastrup
2008-06-09 1:44 ` Glenn Morris
2008-06-09 1:49 ` Glenn Morris
2008-06-09 8:26 ` Eli Zaretskii
2008-06-09 15:32 ` Ted Zlatanov
2008-06-09 15:32 ` David Kastrup
2008-06-09 10:30 ` Robert J. Chassell
2008-06-09 17:22 ` Richard M Stallman
2008-06-09 18:15 ` Glenn Morris
2008-06-09 19:47 ` Miles Bader
2008-06-09 19:53 ` Glenn Morris
2008-06-10 18:22 ` Ted Zlatanov
2008-06-10 18:54 ` Stefan Monnier
2008-06-09 4:37 ` Stephen J. Turnbull
2008-06-09 1:51 ` Stefan Monnier
2008-06-09 16:41 ` Alan Mackenzie
2008-06-07 22:32 ` Yet another bootstrap failure: Required feature `esh-groups' was not provided Stephen J. Turnbull
2008-06-07 2:51 ` Glenn Morris
2008-06-07 8:58 ` Alan Mackenzie
2008-06-06 23:51 ` Vinicius Jose Latorre
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200806061823.m56IN1eY005996@sallyv1.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).