unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Daniel McClanahan <danieldmcclanahan@gmail.com>
Cc: 21821@debbugs.gnu.org
Subject: bug#21821: 25.0.50; invalid byte code in dired-x.elc
Date: Tue, 03 Nov 2015 19:09:24 -0500	[thread overview]
Message-ID: <cfvb9id3rf.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CALuGEhK1rFimnpQLeDXfe3JD2qvsZU8NnuMfRmRNVOGwYJXXoA@mail.gmail.com> (Daniel McClanahan's message of "Tue, 3 Nov 2015 11:53:20 -0600")

Daniel McClanahan wrote:

> Byte-compiling lisp/dired-x.el generates invalid byte code in
> dired-x.elc, which manifests when attempting to use dired-x functions.

I can't reproduce this. You gave no details of platform or anything;
perhaps you need to bootstrap.

> To reproduce on emacs -Q built from master:
> 1. Byte-recompile dired-x.el
> 2. Open dired-x.elc.
> 3. Attempt to evaluate the buffer. It should fail at the attempted
> evaluation of `dired-x-bind-find-file' with an "invalid byte code"
> error.

Did you literally mean what you say, ie visit the .elc file than
evaluate the buffer? I have never thought of doing that with an elc
file, rather than use M-x load-file.






  reply	other threads:[~2015-11-04  0:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 17:53 bug#21821: 25.0.50; invalid byte code in dired-x.elc Daniel McClanahan
2015-11-04  0:09 ` Glenn Morris [this message]
2015-11-04  8:15 ` Andreas Schwab
2015-11-04  9:39   ` Daniel McClanahan
2015-11-04 16:16     ` John Wiegley
2015-11-04 17:10       ` Daniel McClanahan

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=cfvb9id3rf.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=21821@debbugs.gnu.org \
    --cc=danieldmcclanahan@gmail.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).