all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Joseph Mingrone <jrm@FreeBSD.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>,
	ashish@FreeBSD.org, monnier@IRO.UMontreal.CA,
	emacs-devel@gnu.org
Subject: Re: master fails to build on FreeBSD when ACL support is on
Date: Sat, 20 Jan 2018 16:47:38 -0400	[thread overview]
Message-ID: <867escw93p.fsf@phe.ftfl.ca> (raw)
In-Reply-To: <83bmhpt12i.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 20 Jan 2018 09:57:09 +0200")

[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:
> More generally, someone who has access to FreeBSD and understands its
> ACL implementation should look into that, because it sounds like we
> have fundamental problems there with moving files from temp directory,
> and those problems are just waiting to bite us in random places, like
> this one.

After a big of digging, I discovered the immediate problem and it does
not have anything to do with FreeBSD's ACL implementations [1].
FreeBSD's package building tool, poudriere has an option to use tmpfs
for some of the file systems including the working directories, however
I do not believe tmpfs supports ACLs.  When I turn this option off, so
that tmpfs is not used, the build finishes successfully without any
patching.

Should ACL support be required to _build_ Emacs, even if that build will
itself support ACLs?

[1] UFS has both POSIX and NFSv4 ACLs, while ZFS only supports NFSv4 ACLs.
    https://www.freebsd.org/doc/handbook/fs-acl.html
    https://wiki.freebsd.org/NFSv4_ACLs
    https://www.freebsd.org/cgi/man.cgi?query=setfacl

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]

  reply	other threads:[~2018-01-20 20:47 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
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 [this message]
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=867escw93p.fsf@phe.ftfl.ca \
    --to=jrm@freebsd.org \
    --cc=ashish@FreeBSD.org \
    --cc=eggert@cs.ucla.edu \
    --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.