From: Andreas Schwab <schwab@linux-m68k.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>, 34321@debbugs.gnu.org, 34322@debbugs.gnu.org
Subject: bug#34321: bug#34322: reproducibility: absolute file name in tramp.elc
Date: Sun, 30 Jan 2022 18:03:59 +0100 [thread overview]
Message-ID: <87v8y15f5s.fsf@igel.home> (raw)
In-Reply-To: <87o83tb4ni.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 30 Jan 2022 16:54:25 +0100")
On Jan 30 2022, Lars Ingebrigtsen wrote:
> Glenn Morris <rgm@gnu.org> writes:
>
>>> So has this problem fixed itself since it was reported?
>>
>> No it has not.
>>
>> find . -name '*.elc' | xargs grep /scratch
>> Binary file ./lisp/org/ox-odt.elc matches
>> Binary file ./lisp/org/ox.elc matches
>> Binary file ./lisp/progmodes/cc-mode.elc matches
>
> Ah, right, I also get my complete path in those .elc files.
That appears to be a bug in the bytecode inliner. In ox.elc the
function org-element-class (a defsubst) is supposed to be inlined into
org-export-data and org-export-expand, but instead the original bytecode
of org-element-class is put into the bytecode, including its doc string
reference (pointing to org-element.elc, which would normally be written
as $# if it appeared there instead of in ex.elc).
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-01-30 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 22:55 bug#34321: reproducibility: absolute file name in newst-treeview.elc Glenn Morris
2019-02-05 16:15 ` Eli Zaretskii
2019-02-05 18:52 ` Glenn Morris
2022-01-29 15:15 ` bug#34322: reproducibility: absolute file name in tramp.elc Lars Ingebrigtsen
2022-01-29 17:40 ` bug#34321: " Glenn Morris
2022-01-30 15:54 ` Lars Ingebrigtsen
2022-01-30 17:03 ` Andreas Schwab [this message]
2022-05-01 9:03 ` bug#34321: " Lars Ingebrigtsen
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=87v8y15f5s.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=34321@debbugs.gnu.org \
--cc=34322@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rgm@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).