From: Eli Zaretskii <eliz@gnu.org>
To: "Nelson H. F. Beebe" <beebe@math.utah.edu>
Cc: 20218@debbugs.gnu.org
Subject: bug#20218: emacs-24.5-rc1 build successes, and one failure
Date: Sat, 28 Mar 2015 20:48:14 +0300 [thread overview]
Message-ID: <83y4mhypwh.fsf@gnu.org> (raw)
In-Reply-To: <CMM.0.94.0.1427555966.beebe@psi.math.utah.edu>
> Date: Sat, 28 Mar 2015 09:19:26 -0600 (MDT)
> From: "Nelson H. F. Beebe" <beebe@math.utah.edu>
> Cc: beebe@math.utah.edu
>
> The one failure for my emacs-24.5-rc1 builds is this system:
>
> GNU Hurd 8 (jessie) x86-64
>
> I have previously successfully built emacs-24.3.90, emacs-24.3.92, and
> emacs-24.3.94 on that system, and after several failures for
> emacs-24.5-rc1, I retried with the identical PATH and other
> environment variables and configure flags as for 24.3.94. Some of my
> several attempts succeeded in building src/temacs, but all died like
> this:
>
> Loading version...
> Loading widget...
> Loading custom...
> Required feature `widget' was not provided
> Makefile:815: recipe for target 'bootstrap-emacs' failed
Does this mean your build procedure includes a full bootstrap?
If so, what happens if you try building on the Hurd without a
bootstrap?
> In any event, I consider emacs-24.5-rc1 as yet another in long line of
> outstanding successes in the quality and portability of GNU emacs
> releases. Congratulations to the development team --- you've done a
> great job in keeping this fantastic editor potentially available
> virtually everywhere!
Thanks for your efforts and for the report.
next prev parent reply other threads:[~2015-03-28 17:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 15:19 bug#20218: emacs-24.5-rc1 build successes, and one failure Nelson H. F. Beebe
2015-03-28 17:48 ` Eli Zaretskii [this message]
[not found] <CMM.0.95.0.1427566289.beebe@psi.math.utah.edu>
2015-03-28 18:24 ` Eli Zaretskii
2015-03-28 18:32 ` Eli Zaretskii
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=83y4mhypwh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20218@debbugs.gnu.org \
--cc=beebe@math.utah.edu \
/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.