unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>,    Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 34322@debbugs.gnu.org
Subject: bug#34322: reproducibility: absolute file name in tramp.elc
Date: Tue, 05 Feb 2019 18:14:54 +0200	[thread overview]
Message-ID: <83r2cmtdoh.fsf@gnu.org> (raw)
In-Reply-To: <kfa7jbjh3p.fsf@fencepost.gnu.org> (message from Glenn Morris on Mon, 04 Feb 2019 17:58:50 -0500)

> From: Glenn Morris <rgm@gnu.org>
> Date: Mon, 04 Feb 2019 17:58:50 -0500
> 
> Package: emacs
> Version: 26.1.91
> Severity: minor
> 
> Perhaps the same issue as https://debbugs.gnu.org/34321 .
> The definition of tramp-lookup-syntax in tramp.elc contains the absolute
> file name of the build directory, making the file non-reproducible.
> Eg in the 26.1.91 pretest tarfile, it contains
> "/home/nico/work/emacs-26/lisp/net/tramp-compat.elc"

It seems to be a reference to the place in tramp-compat.elc where
tramp-compat-tramp-syntax is defined.  Maybe some byte-compiler guru
could explain or guess when does the byte compiler use such
references.  Stefan, any ideas?





  parent reply	other threads:[~2019-02-05 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 22:58 bug#34322: reproducibility: absolute file name in tramp.elc Glenn Morris
2019-02-05  9:00 ` Michael Albinus
2019-02-05 16:18   ` Eli Zaretskii
2019-02-05 16:36     ` Stefan Monnier
2019-02-05 17:45       ` Michael Albinus
2019-02-05 20:41         ` Stefan Monnier
2021-08-11 19:14           ` bug#34322: bug#34321: reproducibility: absolute file name in newst-treeview.elc Lars Ingebrigtsen
2019-02-05 16:14 ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-04 22:55 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

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=83r2cmtdoh.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34322@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).