From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: bug-guix@gnu.org
Subject: Re: coreutils: Can't exec "/bin/sh": No such file or directory at ./man/help2man
Date: Sat, 22 Jun 2013 22:22:57 +0200 [thread overview]
Message-ID: <87d2rdgaji.fsf@gnu.org> (raw)
In-Reply-To: <87bo6yaxp9.fsf@karetnikov.org> (Nikita Karetnikov's message of "Sat, 22 Jun 2013 20:59:14 +0400")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
> # ./pre-inst-env guix build -K --no-substitutes coreutils
What’s the output path for that? (See "out" in
/nix/store/jyj752q3jjxj0xjgm7wh2xwhkckndab7-coreutils-8.21.drv, for
instance.)
Which Guix commit is it, and which platform?
> [...]
>
> Can't exec "/bin/sh": No such file or directory at ./man/help2man line 229.
> help2man: can't get '--help' info from man/chroot.td/chroot
> make[2]: *** [man/chroot.1] Error 2
The line in question is:
join '', map { s/ +$//; expand $_ } `$ARGV[0] $_ 2>/dev/null`
It could be that Perl’s backquote thing uses /bin/sh, but then we’d have
noticed it elsewhere too (on Hydra, on my laptop, etc.)
Is the daemon doing chroot builds and build users?
> Binary file man/chroot.td/chroot matches
>
> # strings chroot | grep /bin/sh
> /bin/sh
> If no command is given, run '${SHELL} -i' (default: '/bin/sh -i').
>
> Can this be fixed with 'substitute*'?
Yes, but that’s a different issue. Actually, I would leave it as is,
because chroot honors $SHELL:
/* No command. Run an interactive shell. */
char *shell = getenv ("SHELL");
if (shell == NULL)
shell = bad_cast ("/bin/sh");
And also because in the GNU System there’ll be /bin/sh as a symlink to
the “current” Bash (as done on NixOS).
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2013-06-22 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 16:59 coreutils: Can't exec "/bin/sh": No such file or directory at ./man/help2man Nikita Karetnikov
2013-06-22 20:22 ` Ludovic Courtès [this message]
2013-06-23 1:01 ` Nikita Karetnikov
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=87d2rdgaji.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=nikita@karetnikov.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.