On Fri, 2019-09-20 at 19:49 +0200, Svante Signell wrote: > On Fri, 2019-09-20 at 19:03 +0200, Ricardo Wurmus wrote: > > Svante Signell <svante.sign...@gmail.com> writes: > > > > > On a GNU/Linux amd64 qemu image: > > > > > > > > > dpkg -S /usr/share/guile/site/2.2 > > > guile-sqlite3, guile-gcrypt, guile-bytestructures, guile-ssh, guile-json: > > > /usr/share/guile/site/2.2 > > > > You can skip all of this by building the bootstrap binaries on a system > > where Guix is installed. Then it’s merely ’guix environment guix’. > > And how do I apply:gnu_packages_make-bootstrap.scm.diff? Doing > guest@gnu ~ [env]$ guix build --target=i586-pc-gnu bootstrap-tarballs 2>&1 | > tee > ./bootstrap-tarballs-i586-pc-gnu.log > only downloads the already built > binutils-static-stripped-2.31.1-i586-pc-gnu.tar.xz > guile-static-stripped-2.2.4-i586-pc-gnu.tar.xz > gcc-stripped-5.5.0-i586-pc-gnu.tar.xz > static-binaries-0-i586-pc-gnu.tar.xz > glibc-stripped-2.28-i586-pc-gnu.tar.xz > > No guile-2.0 here??
find /gnu/store -name "make-bootstrap.scm"|grep guix-packages- source/gnu/packages|wc -l 12 Which one to patch?? There are also .cache files... Confusing as ever. Seem like the time to learn will be long!
