From: Alex Gramiak <agrambot@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Help with adding an auxiliary bytecode table
Date: Thu, 18 Apr 2019 14:47:37 -0600 [thread overview]
Message-ID: <87a7gn9h1y.fsf@gmail.com> (raw)
In-Reply-To: <e616d91b-9c69-abbe-622b-a073585e5a7b@cs.ucla.edu> (Paul Eggert's message of "Thu, 18 Apr 2019 10:07:02 -0700")
Paul Eggert <eggert@cs.ucla.edu> writes:
> On 4/18/19 8:53 AM, Alex Gramiak wrote:
>> Invalid function: ((bytecomp "Wrong type argument: arrayp, nil" :error
>> "*Compile-Log*"))
>
> This kind of symptom often means you just messed up somewhere in the
> interpreter and have trashed its data structures somehow. You might try
> building with --enable-checking or --enable-checking=all or with the
> usual sanitization flags for your compiler.
Thanks. Turns out it was due to some interaction between my previous
Emacs build's bytecompiler and the new one, since removing
lisp/emacs-lisp/bytecomp.elc and trying to build gave me the wrong type
argument error at build-time.
I managed to fix the problem (ill-defined macro) and get it working.
next prev parent reply other threads:[~2019-04-18 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 15:53 Help with adding an auxiliary bytecode table Alex Gramiak
2019-04-18 17:07 ` Paul Eggert
2019-04-18 20:47 ` Alex Gramiak [this message]
2019-04-21 4:11 ` Stefan Monnier
2019-04-21 19:17 ` Help with adding new setq-based bytecodes (was: Help with adding an auxiliary bytecode table) Alex Gramiak
2019-04-21 20:22 ` Help with adding new setq-based bytecodes Stefan Monnier
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=87a7gn9h1y.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@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).