From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Markus FFM <markusffm@fn.de>
Cc: 32352@debbugs.gnu.org
Subject: bug#32352: 27.0.50; build error
Date: Fri, 03 Aug 2018 15:07:00 +0900 [thread overview]
Message-ID: <b4m4lgcasqj.fsf@jpl.org> (raw)
In-Reply-To: <muu4gfvs.fsf@fn.de>
On Fri, 03 Aug 2018 07:48:07 +0200, Markus FFM wrote:
> build emacs from sources.
> error messages:
[...]
> Directory-local variables error: (invalid-read-syntax #)
> Error: (void-variable =)
This sometimes happens to me, too :). Try `make bootstrap'.
next prev parent reply other threads:[~2018-08-03 6:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 5:48 bug#32352: 27.0.50; build error Markus FFM
2018-08-03 6:07 ` Katsumi Yamaoka [this message]
2018-08-03 6:50 ` Eli Zaretskii
2018-08-03 12:40 ` Noam Postavsky
2018-11-12 19:01 ` Glenn Morris
2018-11-13 1:37 ` Noam Postavsky
2018-11-13 3:35 ` Eli Zaretskii
2018-11-13 13:54 ` Noam Postavsky
2018-11-13 13:58 ` Noam Postavsky
2018-11-13 18:10 ` Glenn Morris
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=b4m4lgcasqj.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=32352@debbugs.gnu.org \
--cc=markusffm@fn.de \
/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).