Eelco Dolstra wrote:
On 16/04/14 00:40, Ben Franksen wrote:
So everything in my sources is patched to use stuff from /nix/store (I
checked that the path exists and is executable) and still it complains
about some /bin/sh missing?
There are many programs that have a (implicit) dependency on
Hey Ben,
On Mon, Apr 14, 2014 at 09:05:25PM +0200, Ben Franksen wrote:
Hi Shea
thanks for taking the time to explain this to me. I see now that what I
wanted is not possible in a clean way.
No problem, sorry if anything wasn't clear!
I think what confused me was that Nix does not
Hi,
On 15/04/14 15:31, Shea Levy wrote:
Yeah, unfortunately chroot builds require a bit of extra OS support as
well as administrative setup, so we can't have it on by default.
Chroot builds also have a non-trivial overhead:
https://github.com/NixOS/nix/issues/179
--
Eelco Dolstra |
Ben Franksen wrote:
I will now read up on how to enable chroot builds in multi-user configured
Nix...
Ok, I now have
build-use-chroot = true
in my /etc/nix/nix.conf. Now, my build fails with this strange error:
building /nix/store/y57pn9yk7r9j06nqfkyd4b1h5p8gfdzr-epics-
Hi,
On 16/04/14 00:40, Ben Franksen wrote:
So everything in my sources is patched to use stuff from /nix/store (I
checked that the path exists and is executable) and still it complains about
some /bin/sh missing?
There are many programs that have a (implicit) dependency on /bin/sh.
Ben Franksen wrote:
building /nix/store/y57pn9yk7r9j06nqfkyd4b1h5p8gfdzr-epics-
base-3.14.12.2.1/configure/CONFIG_ENV
make[2]: /bin/sh: Command not found
Hmmm, this sounds strangely familiar. Am I interpreting this wrong and it
means the shell itself (which is not /bin/sh but actually
Hi Ben,
Fetching source over the network is the main reason fixed output
derivations even exist. When chroot builds are enabled, networking is not
allowed for non-fixed output derivations.
Interesting, I did not know this.
I agree that this policy makes sense for stuff that gets
Peter Simons wrote:
Fetching source over the network is the main reason fixed output
derivations even exist. When chroot builds are enabled, networking is
not allowed for non-fixed output derivations.
Interesting, I did not know this.
I agree that this policy makes sense for
Hi Shea
thanks for taking the time to explain this to me. I see now that what I
wanted is not possible in a clean way.
I think what confused me was that Nix does not enforce purity of builds by
default. Out of the box, i.e. without chroot builds, getting sources for
instance via darcs or
