From: Eli Zaretskii <eliz@gnu.org>
To: Joris Vankerschaver <joris.vankerschaver@gmail.com>
Cc: 24742-done@debbugs.gnu.org
Subject: bug#24742: 25.1; autoloads tries to parse shared object files when module support is enabled
Date: Thu, 20 Oct 2016 09:37:30 +0300 [thread overview]
Message-ID: <83a8dzv845.fsf@gnu.org> (raw)
In-Reply-To: <CAFytq+m2R-umHmw4Xk5CmA3dEZzN9Oc16kE103zRKpJRd9Kk1w@mail.gmail.com> (message from Joris Vankerschaver on Wed, 19 Oct 2016 19:35:04 +0100)
> From: Joris Vankerschaver <joris.vankerschaver@gmail.com>
> Date: Wed, 19 Oct 2016 19:35:04 +0100
>
> This happens on an Emacs that has been compiled with module support.
> Installing a multi-file package (with M-x package-install-file) that contains a
> shared library (e.g. an Emacs module) results in a traceback.
>
> The traceback is included below. It is hard to reproduce this exactly, but what
> happens is that update-directory-autoloads iterates over the files in the
> package, and checks the extension of each file against the list of executable
> suffixes (from get-load-suffixes). When module support is enabled, that list
> contains ".so" (or ".dll", depending on the platform), causing
> autoload-generate-file-autoloads to try and parse the shared object file.
>
> A possible fix would be to have update-directory-autoloads exclude shared
> object files (indeed, this fixes the problem on my platform). A complication is
> that the list of shared object file extensions is platform dependent. I don't
> know if there is a reliable way of getting this information.
Thanks, this has been solved already for the next release of Emacs.
prev parent reply other threads:[~2016-10-20 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 18:35 bug#24742: 25.1; autoloads tries to parse shared object files when module support is enabled Joris Vankerschaver
2016-10-20 6:37 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a8dzv845.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24742-done@debbugs.gnu.org \
--cc=joris.vankerschaver@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.