From: ludo@gnu.org (Ludovic Courtès)
To: Gregor Giesen <giesen@zaehlwerk.net>
Cc: help-guix@gnu.org
Subject: Re: Extra files in build container
Date: Fri, 16 Jun 2017 09:58:55 +0200 [thread overview]
Message-ID: <87y3ssicsg.fsf@gnu.org> (raw)
In-Reply-To: <20170615072917.4ogzt24ginrkgqx3@zaehlwerk.net> (Gregor Giesen's message of "Thu, 15 Jun 2017 09:29:17 +0200")
Hi Gregor,
Gregor Giesen <giesen@zaehlwerk.net> skribis:
> I'm trying to pack unbound, however its unittests require /etc/protocols
> and /etc/services. Now, I have found them in the net-base package
> which I included in native-inputs, but that is not sufficient for
> glibc's getprotoent and getservent to find them. Can I symlink the
> net-base ones to the build container's /etc? Adding an extra phase
> before 'check does not allow me to write /etc in the container.
Indeed, /etc is read-only in the build container, and it contains only
the bare minimum:
https://www.gnu.org/software/guix/manual/html_node/Build-Environment-Setup.html
The code that populates it can be found at:
https://git.savannah.gnu.org/cgit/guix.git/tree/nix/libstore/build.cc#n1852
In cases like the one you describe, we usually end up modifying tests to
use the numerical values for services and protocols rather than their
names.
It would probably make sense to allow derivations to populate /etc
though.
HTH,
Ludo’.
next prev parent reply other threads:[~2017-06-16 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 7:29 Extra files in build container Gregor Giesen
2017-06-16 7:58 ` Ludovic Courtès [this message]
2017-06-17 6:58 ` Gregor Giesen
2017-06-19 11:26 ` Ludovic Courtès
2017-06-19 11:44 ` Gregor Giesen
2017-06-19 14:49 ` Ludovic Courtès
2017-06-19 16:48 ` Gregor Giesen
2017-06-19 21:21 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y3ssicsg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=giesen@zaehlwerk.net \
--cc=help-guix@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.
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).