Hi,
> There are a couple of issues with using call-with-container. In
> decreasing order of perceived difficulty to solve:
>
> 1. Copying the output from the build to the real store. How would that
> work? It wouldn't work with call-with-container - the container can't
> access the outside world,
Hi reepca,
Caleb Ristvedt skribis:
>> Is there a line above or below the backtrace mentioning the uncaught
>> exception? Could you ‘strace -f’ the daemon process?
>
> No, no line above or below. Very strange.
And strace? :-) It could be that it fails to load some of the
(system *) helper mod
> Is there a line above or below the backtrace mentioning the uncaught
> exception? Could you ‘strace -f’ the daemon process?
No, no line above or below. Very strange.
> BTW, I see the code uses ‘clone’ directly. It would be safer to use
> ‘call-with-container’, which already handles bind moun
Caleb Ristvedt writes:
> This includes reference-scanning, which I think pretty much works, but
> which I regret to say I spent too much time thinking about. Premature
> optimization and all that. It takes a rather different approach to the
> way the C++ code does it - it uses a trie to recognize
Hi reepca!
Caleb Ristvedt skribis:
> After a pileup of changes and testing, I finally got around to pushing
> my changes to the guile-daemon to the branch on savannah. The big
> addition is half-working derivation-building (just one at a time, for
> now, and only chroot builds for now) in the fo
Hello guix!
After a pileup of changes and testing, I finally got around to pushing
my changes to the guile-daemon to the branch on savannah. The big
addition is half-working derivation-building (just one at a time, for
now, and only chroot builds for now) in the form of
guix/store/build-derivation
