I’d like to know how ‘roll-back’ creates an empty generation because
it’s necessary to do the same for ‘--delete-generations’.
However, I fail to understand how (profile-derivation (%store) ‘())
works (or any other function that uses (%store)). I assume that some
code should set ‘%store’ to
Nikita Karetnikov nik...@karetnikov.org skribis:
I’d like to know how ‘roll-back’ creates an empty generation because
it’s necessary to do the same for ‘--delete-generations’.
However, I fail to understand how (profile-derivation (%store) ‘())
works (or any other function that uses
Nikita Karetnikov nik...@karetnikov.org skribis:
‘%store’ is a SRFI-39 parameter (info (guile) Parameters), aka. a
dynamically-scoped variable.
It is initialized with the ‘parameterize’ form, which sets its value for
the dynamic extent of its body.
I don’t understand what code initializes
Hi Ludovic,
l...@gnu.org (Ludovic Courtès) writes:
However, in theory, that doesn’t save us from trusting-trust
attacks [1]: the bootstrap GCC could contain a trap, such that the trap
is always preserved across recompilations of GCC, even if it’s absent
From the GCC source being compiled.
‘%store’ is a SRFI-39 parameter (info (guile) Parameters), aka. a
dynamically-scoped variable.
It is initialized with the ‘parameterize’ form, which sets its value for
the dynamic extent of its body.
I don’t understand what code initializes ‘%store’.
For example, I have one generation in
Mark H Weaver m...@netris.org skribis:
Hi Ludovic,
l...@gnu.org (Ludovic Courtès) writes:
However, in theory, that doesn’t save us from trusting-trust
attacks [1]: the bootstrap GCC could contain a trap, such that the trap
is always preserved across recompilations of GCC, even if it’s
So (gnu system vm) and its friends are now able to build a bootable QEMU
image. That’s still *very* rough on the edges, but it boots into dmd
(version -0.4 is out BTW, 10 years later ;-)).
To build it, do something like:
--8---cut here---start-8---
$
