From: "Ludovic Courtès" <ludo@gnu.org>
To: guix-devel@gnu.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: Re: 33/33: daemon: Workaround issues for the Hurd.
Date: Tue, 10 Mar 2020 10:04:43 +0100 [thread overview]
Message-ID: <87v9ncwpg4.fsf@gnu.org> (raw)
In-Reply-To: <20200310075853.45FCC21252@vcs0.savannah.gnu.org> (guix-commits@gnu.org's message of "Tue, 10 Mar 2020 03:58:53 -0400 (EDT)")
guix-commits@gnu.org skribis:
> commit c32b64950972a459af7192abd7a8bc9619c013e9
> Author: Manolis Ragkousis <manolis837@gmail.com>
> AuthorDate: Wed Dec 28 02:49:22 2016 +0200
>
> daemon: Workaround issues for the Hurd.
>
> This allows for native builds on the Hurd, doing
>
> sudo ./pre-inst-env guix-daemon --disable-chroot --build-users-group=guixbuild &
> ./pre-inst-env guix build hello
>
> * nix/libstore/build.cc (DerivationGoal::startBuilder)[__GNU__]: Allow
> non-chrooted build.
> * nix/libutil/util.cc (killUser)[__GNU__]: Avoid wait failure.
[...]
> +++ b/nix/libstore/build.cc
> @@ -1824,7 +1824,7 @@ void DerivationGoal::startBuilder()
> }
>
> if (useChroot) {
> -#if CHROOT_ENABLED
> +#if CHROOT_ENABLED || __GNU__
Can we instead change the #define CHROOT_ENABLED such that
CHROOT_ENABLED is always true when __GNU__? Also with a comment stating
that GNU supports chroot(2) without being root.
> +++ b/nix/libutil/util.cc
> @@ -872,9 +872,11 @@ void killUser(uid_t uid)
> _exit(0);
> });
>
> +#if !__GNU__
> int status = pid.wait(true);
> if (status != 0)
> throw Error(format("cannot kill processes for uid `%1%': %2%") % uid % statusToString(status));
> +#endif
Do you know what the rationale was? It looks like it could leave
zombies behind us.
Ludo’.
next prev parent reply other threads:[~2020-03-10 9:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200310075832.7126.86402@vcs0.savannah.gnu.org>
[not found] ` <20200310075845.291F421123@vcs0.savannah.gnu.org>
2020-03-10 8:54 ` 08/33: gnu: make: Revert to 4.1 for the Hurd Ludovic Courtès
2020-03-10 9:16 ` Jan Nieuwenhuizen
[not found] ` <20200310075844.240A021123@vcs0.savannah.gnu.org>
2020-03-10 8:55 ` 05/33: gnu: hurd: Fix hurd-target? Ludovic Courtès
2020-03-10 11:22 ` Jan Nieuwenhuizen
[not found] ` <20200310075846.1DA6821123@vcs0.savannah.gnu.org>
2020-03-10 9:02 ` 11/33: gnu: glibc: Add and update patches for the Hurd Ludovic Courtès
2020-03-10 11:28 ` Jan Nieuwenhuizen
[not found] ` <20200310075853.45FCC21252@vcs0.savannah.gnu.org>
2020-03-10 9:04 ` Ludovic Courtès [this message]
2020-03-10 12:54 ` 33/33: daemon: Workaround issues " Jan Nieuwenhuizen
2020-03-11 14:50 ` Ludovic Courtès
2020-03-12 6:59 ` bug#40006: " Jan Nieuwenhuizen
2020-03-12 6:59 ` Jan Nieuwenhuizen
2020-03-12 12:59 ` Ludovic Courtès
2020-03-12 12:59 ` bug#40006: " Ludovic Courtès
[not found] ` <20200310075847.6059A2112F@vcs0.savannah.gnu.org>
2020-03-10 9:06 ` 15/33: gnu: coreutils: Remove libcap dependency " Ludovic Courtès
2020-03-11 15:01 ` Jan Nieuwenhuizen
2020-03-11 18:09 ` Vincent Legoll
2020-03-11 19:43 ` Jan Nieuwenhuizen
2020-03-12 13:01 ` Ludovic Courtès
2020-03-14 8:28 ` bug#40006: " Jan Nieuwenhuizen
2020-03-14 8:28 ` Jan Nieuwenhuizen
[not found] ` <20200310075851.4497E2125F@vcs0.savannah.gnu.org>
2020-03-10 9:10 ` 27/33: gnu: commencement: glibc-intermediate: Build fixes " Ludovic Courtès
2020-03-10 12:45 ` Jan Nieuwenhuizen
[not found] ` <20200310075850.035F02125B@vcs0.savannah.gnu.org>
2020-03-10 9:13 ` 23/33: gnu: commencement: gcc-boot0: Build fix " Ludovic Courtès
2020-03-10 9:18 ` Efraim Flashner
2020-03-10 13:53 ` Jan Nieuwenhuizen
2020-03-11 14:27 ` Jan Nieuwenhuizen
2020-03-11 15:14 ` Efraim Flashner
2020-03-11 16:20 ` Jan Nieuwenhuizen
2020-03-11 16:27 ` Efraim Flashner
2020-03-12 7:02 ` Jan Nieuwenhuizen
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=87v9ncwpg4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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 external index
https://git.savannah.gnu.org/cgit/guix.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.