From: Noam Postavsky <npostavs@users.sourceforge.net>
To: ghost <klegarkov@fides.com>
Cc: 27288@debbugs.gnu.org
Subject: bug#27288: emacs compile failes
Date: Tue, 28 Nov 2017 21:25:24 -0500 [thread overview]
Message-ID: <87k1y9lt2j.fsf@users.sourceforge.net> (raw)
In-Reply-To: <e0eaa48c-5092-092c-df7a-b577a19a58c0@fides.com> (ghost's message of "Thu, 8 Jun 2017 13:16:48 +0300")
close 27288 26.1
quit
ghost <klegarkov@fides.com> writes:
> rpmbuild -bb
>
> It fails on 'make' stage:
>
> Checking for automake (need at least version 1.11)...
> missing
In Emacs 26, automake is no longer needed.
prev parent reply other threads:[~2017-11-29 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 10:16 bug#27288: emacs compile failes ghost
2017-06-08 15:39 ` Glenn Morris
2017-11-29 2:25 ` Noam Postavsky [this message]
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=87k1y9lt2j.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=27288@debbugs.gnu.org \
--cc=klegarkov@fides.com \
/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).