all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: master fails to build on FreeBSD when ACL support is on
Date: Sat, 20 Jan 2018 20:04:32 -0500	[thread overview]
Message-ID: <jw4lngja3j.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <f9373135wa.fsf@fencepost.gnu.org> (Glenn Morris's message of "Fri, 19 Jan 2018 16:17:25 -0500")


IMO the change in 4fd446e is obviously correct.
The current (reverted) code is wrong by inspection when target-file is
relative. In normal use, it never is, but it will be if
byte-compile-dest-file is changed to return a non-absolute value.

For example, this can be the case for automake, as we saw in

http://lists.gnu.org/archive/html/emacs-devel/2017-11/msg00551.html

since Makefiles normally use relative filenames, and automake changes
byte-compile-dest-file-function to return "$@".

Eg I predict the following will fail on a FreeBSD system like the one in
the original message in this thread:

./src/emacs --batch \
 --eval '(setq byte-compile-dest-file-function (lambda (x) "foo.elc"))'
  -f batch-byte-compile foo.el

This simulates how automake may call Emacs to compile a file.

(It fails on RHEL 7.4 with TMPDIR=/does/not/exist. Obviously this is not
sensible, but the point is that it should not be writing to TMPDIR at all.)


I am posting this analysis for completeness, with zero expectation of it
changing anything.



  reply	other threads:[~2018-01-21  1:04 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16  4:20 master fails to build on FreeBSD when ACL support is on Joseph Mingrone
2018-01-16 17:06 ` Paul Eggert
2018-01-16 18:16 ` Eli Zaretskii
2018-01-18 23:40   ` Joseph Mingrone
2018-01-19 14:45     ` Eli Zaretskii
2018-01-19 14:59       ` Joseph Mingrone
2018-01-19 15:33         ` Eli Zaretskii
2018-01-19 16:38       ` Stefan Monnier
2018-01-19 18:45         ` Eli Zaretskii
2018-01-19 20:53           ` Stefan Monnier
2018-01-19 21:17             ` Glenn Morris
2018-01-21  1:04               ` Glenn Morris [this message]
2018-01-21  3:42                 ` Paul Eggert
2018-11-14 23:12                 ` Glenn Morris
2018-11-15  1:23                   ` Paul Eggert
2018-11-15 14:48                     ` Eli Zaretskii
2018-01-19 22:42             ` Paul Eggert
2018-01-20  7:52               ` Michael Albinus
2018-01-21  3:49                 ` Paul Eggert
2018-01-21 12:14                   ` Michael Albinus
2018-01-20  7:57               ` Eli Zaretskii
2018-01-20 20:47                 ` Joseph Mingrone
2018-01-20 23:35                   ` Joseph Mingrone
2018-01-21  3:41                     ` Paul Eggert
2018-01-21  3:50                       ` Stefan Monnier
2018-01-22  6:42                         ` Paul Eggert
2018-01-22 14:11                           ` Stefan Monnier
2018-01-21 15:53                       ` Eli Zaretskii
2018-01-22  6:52                         ` Paul Eggert
2018-01-22 15:52                           ` Eli Zaretskii
2018-01-22 17:02                             ` Paul Eggert
2018-01-22 17:41                               ` Eli Zaretskii
2018-01-22 18:50                                 ` Paul Eggert
2018-01-22 20:32                                   ` Eli Zaretskii
2018-01-23  0:47                                     ` Paul Eggert
2018-01-21 15:56                   ` Eli Zaretskii
2018-01-21 16:22                     ` Joseph Mingrone
2018-01-20  7:46             ` Eli Zaretskii
2018-01-17 18:33 ` Ashish SHUKLA
2018-01-17 18:53   ` Joseph Mingrone

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=jw4lngja3j.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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.