From: Paul Eggert <eggert@cs.ucla.edu>
To: markusffm@fn.de
Cc: 33945@debbugs.gnu.org
Subject: bug#33945: 27.0.50; build error (allout.el)
Date: Wed, 2 Jan 2019 12:29:01 -0800 [thread overview]
Message-ID: <f0300341-8390-9bc3-3128-e935ac433b7c@cs.ucla.edu> (raw)
In-Reply-To: <20190102170504.GA7720@INDRA>
markusffm@fn.de wrote:
>
> it's clearly a syntax error in 'allout.el':
> 'Error occurred processing allout.el: Wrong number of arguments (((0 . 0) 2))'
OK, but why are you seeing this diagnostic whereas nobody else seems to have the
problem? It seems likely that it's not an actual syntax error, but is instead a
bug somewhere else that is causing the Lisp reader or byte compiler to misbehave
and falsely report a syntax error.
What happens if you use -O2 (the default) rather than -Os to build from scratch?
Also, which version of GCC are you using? Mine is gcc (GCC) 8.2.1 20181215 (Red
Hat 8.2.1-6).
next prev parent reply other threads:[~2019-01-02 20:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 14:50 bug#33945: 27.0.50; build error (allout.el) Markus FFM
2019-01-01 23:18 ` Paul Eggert
2019-01-02 6:41 ` markusffm
[not found] ` <20190102063423.GA30513@INDRA>
2019-01-02 6:56 ` Paul Eggert
2019-01-02 8:03 ` markusffm
[not found] ` <20190102080009.GA25929@INDRA>
2019-01-02 9:55 ` Paul Eggert
[not found] ` <20190102170504.GA7720@INDRA>
2019-01-02 17:07 ` markusffm
2019-01-02 20:29 ` Paul Eggert [this message]
2019-01-02 21:07 ` markusffm
[not found] ` <20190102210451.GA11088@INDRA>
2019-01-03 1:44 ` Paul Eggert
[not found] ` <20190103071903.GA27619@INDRA>
2019-01-03 7:20 ` markusffm
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=f0300341-8390-9bc3-3128-e935ac433b7c@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=33945@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).