bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[dan]

Hi David,

Thanks for the reply.

Apr 11, 2024 04:50:03 David Elsing :


Can we put everything inside build-inputs?  From my understanding,
copy-build-system shouldn't care about cross-compilation at all.

I understand it that way too. In guix/build-system.scm, it is mentioned
that build/host/target are used in the sense of the GNU toolchain [1].
There, "build" is the system used for building and "host" is the target
system for which the package is built. I guess this was confused when
copy-build-system was added [2].


Then I think I can submit a patch to guix-patches, hoping to bring more 
attention to this bug.

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[David Elsing]

Hi dan,

sorry for the late reply. I didn't yet find the reason why different
bootstrap packages are built for the cross build when grafts are
applied. This seems possibly like another bug to me, as the package
inputs which use copy-build-system do not contain store references and
it does not happen when they themselves are built with grafts.

dan  writes:

> Can we put everything inside build-inputs?  From my understanding, 
> copy-build-system shouldn't care about cross-compilation at all.
I understand it that way too. In guix/build-system.scm, it is mentioned
that build/host/target are used in the sense of the GNU toolchain [1].
There, "build" is the system used for building and "host" is the target
system for which the package is built. I guess this was confused when
copy-build-system was added [2].

Cheers,
David

[1] 
https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.72/html_node/Specifying-Target-Triplets.html
[2] https://issues.guix.gnu.org/39599

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[dan]

Hi all,

I would really appreciate if anyone could give some feedback on my 
previous patch to the copy build system.


--
dan

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[dan]

Hi David,

Thanks for sharing your discovery.

David Elsing  writes:

Starting from alsa-lib, I narrowed it down further. I found that 
the
problem is actually when an input of the package uses 
copy-build-system.


I spent some time digging into the rabbit hole.  After changing 
the lower function of the copy-build-system to look more like the 
lower function of the gnu-build-system, I'm able to cross compile 
alsa-lib without the --no-grafts flag.  The changes I made are 
like:


--8<---cut here---start->8---
diff --git a/guix/build-system/copy.scm 
b/guix/build-system/copy.scm

index d58931b33c..74304b4bfb 100644
--- a/guix/build-system/copy.scm
+++ b/guix/build-system/copy.scm
@@ -66,13 +66,13 @@ (define* (lower name
  (bag
(name name)
(system system)
-(host-inputs `(,@(if source
+(build-inputs `(,@(if source
 `(("source" ,source))
 '())
-   ,@inputs
+   ,@native-inputs
   ;; Keep the standard inputs of 
   'gnu-build-system'.

   ,@(standard-packages)))
-(build-inputs native-inputs)
+(host-inputs inputs)
(outputs outputs)
(build copy-build)
(arguments (strip-keyword-arguments private-keywords 
arguments

--8<---cut here---end--->8---

Can we put everything inside build-inputs?  From my understanding, 
copy-build-system shouldn't care about cross-compilation at all.


Any feedback on this would be really helpful.

Best,
--
dan

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[David Elsing]

Hello,

Mathieu Othacehe  writes:

> I could narrow it down somehow.

Starting from alsa-lib, I narrowed it down further. I found that the
problem is actually when an input of the package uses copy-build-system.

In the following example, the cross-compilation (with
--target=x86_64-linux-gnu) for testp2 and testp3 works fine. Their
respective inputs are testinput2 (built with trivial-build-system) and
the hello package (built with gnu-build-system).
For testp1 however, whose input testinput1 is created
with copy-build-system, the same thing as for alsa-lib (which depends on
two packages built with copy-build-system) happens: Bootstrap packages
are starting to be built if grafts are used. The outputs of both
testinput1 and testinput2 do not contain store references, so that is
not the issue. It is also no problem to build the packages testinput1,
testinput2 or hello with grafts.

Is there something special about copy-build-system which is not the case
for trivial-build-system and gnu-build-system? I noticed that in
(guix build-system trival) and (guix build-system gnu), there is a
special case for cross-compilation, while in (guix build-system copy),
the same code is used as for a normal build. I don't see why this could
cause an issue with grafts though.

--8<---cut here---start->8---
(define-module (cc-test)
 #:use-module (guix build-system copy)
 #:use-module (guix build-system gnu)
 #:use-module (guix build-system trivial)
 #:use-module (gnu packages base)
 #:use-module (guix packages)
 #:use-module (guix gexp))

(define-public testinput1
  (package
(name "testinput1")
(version "0")
(source
 (computed-file
  "testp1-src"
  #~(begin
  (mkdir #$output)
  (mkdir (string-append #$output "/dummy")
(build-system copy-build-system)
(arguments (list #:install-plan ''(("dummy" "dummy"
(home-page "")
(synopsis "")
(description "")
(license #f)))

(define-public testinput2
  (package
(name "testinput2")
(version "0")
(source #f)
(build-system trivial-build-system)
(arguments
 (list
  #:builder
  #~(begin
  (mkdir #$output)
  (mkdir (string-append #$output "/dummy")
(home-page "")
(synopsis "")
(description "")
(license #f)))

(define-public testp1
  (package
(name "testp1")
(version "0")
(source #f)
(build-system trivial-build-system)
(arguments
 (list
  #:builder #~(mkdir #$output)))
(inputs (list testinput1))
(home-page "")
(synopsis "")
(description "")
(license #f)))

(define-public testp2
  (package
(name "testp2")
(version "0")
(source #f)
(build-system trivial-build-system)
(arguments
 (list
  #:builder #~(mkdir #$output)))
(inputs (list testinput2))
(home-page "")
(synopsis "")
(description "")
(license #f)))

(define-public testp3
  (package
(name "testp3")
(version "0")
(source #f)
(build-system trivial-build-system)
(arguments
 (list
  #:builder #~(mkdir #$output)))
(inputs (list hello))
(home-page "")
(synopsis "")
(description "")
(license #f)))
--8<---cut here---end--->8---

Best,
David

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[Mathieu Othacehe]

> The issue seems to be that grafting ends-up dragging the bootstrap
> packages into the closure when cross-compiling which is quite scary.

I could narrow it down somehow.

This commands drags the bootstrap and fails:

--8<---cut here---start->8---
guix build --target= alsa-lib 
--8<---cut here---end--->8---

while this one doesn't:

--8<---cut here---start->8---
guix build --target= alsa-lib --no-grafts
--8<---cut here---end--->8---

Not sure how to go further. Adding Ludo and Efraim.

Thanks,

Mathieu

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[Mathieu Othacehe]

Hey,

> ./pre-inst-env guix system build --target=aarch64-linux-gnu 
> gnu/system/images/pine64.scm
>
>
> which cause an issue in gawk-mesboot:
>
> checking host system type... Invalid configuration `aarch64-linux-gnu': 
> machine `aarch64' not recognized
> configure: error: 
> /gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash 
> ./config.sub aarch64-linux-gnu failed
>
> Janneke, do you know what could have caused this regression?

This probably has nothing to do with the bootstrap packages. I noticed
that the CI succeeds in building the pine64 image:
https://ci.guix.gnu.org/build/3265001/details.

The difference is that the CI is building without grafting. Disabling
grafting locally, seems to do the trick as well:

--8<---cut here---start->8---
./pre-inst-env guix system image gnu/system/images/pine64.scm  --no-grafts
--8<---cut here---end--->8---

The issue seems to be that grafting ends-up dragging the bootstrap
packages into the closure when cross-compiling which is quite scary.

Mathieu

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[Mathieu Othacehe]

Hello,

I can reproduce the error by running:

--8<---cut here---start->8---
./pre-inst-env guix system build --target=aarch64-linux-gnu 
gnu/system/images/pine64.scm
--8<---cut here---end--->8---

which cause an issue in gawk-mesboot:

--8<---cut here---start->8---
checking host system type... Invalid configuration `aarch64-linux-gnu': machine 
`aarch64' not recognized
configure: error: 
/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash 
./config.sub aarch64-linux-gnu failed
--8<---cut here---end--->8---

Janneke, do you know what could have caused this regression?

Thanks,

Mathieu

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[Lars Rustand]

Hello, bumping this issue since there has been no activity for a while
and this error is still present. I get the exact same error as Denis
when building any Pine64 images. Building with --system=aarch64-linux
instead of --target=aarch64-linux-gnu works, but this is very much
slower.


This is what I get:

> checking for string.h... (cached) yes
> checking whether NLS is requested... yes
> checking for msgfmt... no
> checking for gmsgfmt... :
> checking for xgettext... no
> checking for msgmerge... no
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... Invalid configuration `aarch64-linux-gnu': 
> machine `aarch64' not recognized
> configure: error: 
> /gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash 
> ./config.sub aarch64-linux-gnu failed
> error: in phase 'configure': uncaught exception:
> srfi-34 # "/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash" 
> arguments: ("./configure" "CC_FOR_BUILD=gcc" 
> "CONFIG_SHELL=/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash"
>  "SHELL=/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash" 
> "--prefix=/gnu/store/bl3aq7fnpyxq9w2a7bqa4zqgd8z88y8x-gawk-mesboot-3.1.8" 
> "--enable-fast-install" "--build=x86_64-unknown-linux-gnu" 
> "--host=aarch64-linux-gnu" "ac_cv_func_connect=no") exit-status: 1 
> term-signal: #f stop-signal: #f] 152c4c0>
> phase `configure' failed after 38.7 seconds
> command 
> "/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash" 
> "./configure" "CC_FOR_BUILD=gcc" 
> "CONFIG_SHELL=/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash"
>  "SHELL=/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash" 
> "--prefix=/gnu/store/bl3aq7fnpyxq9w2a7bqa4zqgd8z88y8x-gawk-mesboot-3.1.8" 
> "--enable-fast-install" "--build=x86_64-unknown-linux-gnu" 
> "--host=aarch64-linux-gnu" "ac_cv_func_connect=no" failed with status 1


Other cross-compiled images like Raspberry Pi work fine for me.

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[dan]

Hi Josselin,

Josselin Poiret  writes:

Could you post some more details about what you mean by 
"couldn't work"?

What exactly is failing, and with what logs?


I was testing it with a cloned guix repo on my disk, opening a 
shell with "guix shell -D guix git".


when checkout to the following commit:

$ ./pre-inst-env guix describe
Git checkout:
  repository: /home/dan/workspace/guix/guix/
  branch: HEAD
  commit: 1328c4cca531318e3ed90c6aecb522a5b22a4bcc


i run "./pre-inst-env guix system build 
gnu/system/images/pine64.scm --target=aarch64-linux-gnu -n" would 
get the following result:
$ ./pre-inst-env guix system build gnu/system/images/pine64.scm 
--target=aarch64-linux-gnu -n

The following derivations would be built:
  /gnu/store/jgd1kl2zavkxsvxa875r8lpndq292vgb-glibc-2.35.drv
  /gnu/store/0za1m1xwpzwai1sgq5zwgyk6zg62w6a0-diffutils-boot0-3.8.drv
  /gnu/store/1mizwrvfq2f96jjwxbky0q1pbdhfr09g-grep-mesboot-3.8.drv
  /gnu/store/9xwp6pi7ssi9jhhj50dd1apryidcz2hk-gawk-mesboot-3.1.8.drv
  /gnu/store/bfh1p0wjl0jgy7yyzrl9kxxls08in0z9-glibc-mesboot-2.16.0.drv
  /gnu/store/bwx8g1wy9pc4aa5my3c8mqg0cb68hhw3-make-mesboot-3.82.drv
  /gnu/store/da5mc3xqc5rqlzc6jyvhgw2nklhcxrxn-gcc-mesboot-4.9.4.drv
  /gnu/store/f5l62q2ykp5vc9pvnw7cwp9ymkyb1m0p-tar-mesboot-1.34.drv
  /gnu/store/knnik0y9ckaiahhyrc0vrmciz92jfiaf-gcc-mesboot-wrapper-4.9.4.drv
  /gnu/store/sdz4dcdd1fnp078m4km980h3q5668w44-sed-mesboot-4.8.drv
  /gnu/store/svcq1qj4j5b784z2sykrm5nj6qsv0mly-make-boot0-4.3.drv
  /gnu/store/vljsi6fwfpxwf3bivhsv7nvrdilk0c89-xz-mesboot-5.2.8.drv
  /gnu/store/1am1zifq9lvlrx7xayzfgq10bzwyi9jz-gawk-boot0-5.2.1.drv
  /gnu/store/2fyrmqijwm1kn90iy1n339kip9c4iq7d-bzip2-boot0-1.0.8.drv
  /gnu/store/3kcikvc17a4wfh4bz13sibnbbz2ybi8j-sed-boot0-4.8.drv
  /gnu/store/879pl2y8f87r7x7p14cxg43qzwrabvhz-bash-static-5.1.16.drv
  /gnu/store/9h6w80fckq0pz6h9w7ab6si6x9arw46s-coreutils-boot0-9.1.drv
  /gnu/store/b7abpvf7w2yv8qzj9gvrbxqvys3cfvvi-binutils-cross-boot0-2.38.drv
  /gnu/store/gjln0wdfin1cd4pa5p05xpgcm18zhbpb-tar-boot0-1.34.drv
  /gnu/store/lzyaiv4rri34n3wqyr7sh7as5rm3qscy-file-boot0-5.44.drv
  /gnu/store/xkrprcjws5xjanfbyzxvyjrz59dza43l-findutils-boot0-4.9.0.drv
  /gnu/store/z9v1jii5ja9y8szrgfyq9vbainldzzrx-patch-boot0-2.7.6.drv
  /gnu/store/bansacd0mz6f0jilr2b18na7k41vyd7l-gcc-cross-boot0-wrapped-11.3.0.drv
  /gnu/store/c97avnw7ivnsf4zpz2lhpy7gnxvdyi1v-glibc-intermediate-2.35.drv
  /gnu/store/f9djhbwy9p706xzkl0r0zx5brqhlm0qd-gcc-cross-boot0-11.3.0.drv
  /gnu/store/r4ab2f6hmrd0z630c1isyyq7dd3pr3zd-libstdc++-boot0-4.9.4.drv
  /gnu/store/nq5i5b8y411hfzc5a0xcqmjiw6y2f5wq-ld-wrapper-boot0-0.drv


but with the previous commit:

$ ./pre-inst-env guix describe
Git checkout:
  repository: /home/dan/workspace/guix/guix/
  branch: HEAD
  commit: f62737bfee086040fa3ecb26968f6d16f84147aa


i run the same command, would get the following result:
$ ./pre-inst-env guix system build gnu/system/images/pine64.scm 
--target=aarch64-linux-gnu -n

The following derivations would be built:
  /gnu/store/cax2125wghlr5wz8hwllrz6vb3l7wd83-system.drv
  /gnu/store/1r0j7c31427lirfdrdggjk9q3jqimf2h-etc.drv
  /gnu/store/4wf34mjqdb7bnx6jfyhlyki5v14dzvvg-profile.drv
  
/gnu/store/3wh899wnr71shq81lnl3kaw1rpnilvrn-linux-libre-arm64-generic-6.4.16.drv
  /gnu/store/x7c5jrsg2kv71jb5bdxf4cv107mlnf4p-linux-libre-6.4.16-guix.tar.xz.drv
  /gnu/store/gyhzn3j6iqa3yf25fv2crbkssg5b7xn5-linux-libre-6.4.16-guix.tar.xz.drv
  /gnu/store/d11phf2n76syynzmrf02va9phjmgr2d2-raw-initrd.drv
  /gnu/store/fqnahvhkabz9riaw5ffr3pnpsp1qiyj8-init.drv
  /gnu/store/0arw5hrqdvzf2ma370ki2d2sn7gij3j5-linux-modules.drv
  /gnu/store/92phv6cpskhywlwv0lqh9ssrmdbm3rls-module-import-compiled.drv
  /gnu/store/hgd43fd0b1xgfw23xmq99k75kiq94zpq-boot.drv
  /gnu/store/a5gwz9v5l5slihmws7wh9x0ic1ckjrb7-shepherd.conf.drv
  /gnu/store/0kiyxgqnjxigfcks0n494apj6wqb6ylg-shepherd-term-tty3.go.drv
  /gnu/store/hpjcgw36jypikzj4qqsb8wmlh140gy1f-shepherd-term-tty3.scm.drv
  /gnu/store/14f4h28fs49vnqvdc65xr5ddcmsh2i79-shepherd-user-file-systems.go.drv
  /gnu/store/njwv1l3hx5lcph4k0d0ld0j3cggc6c3h-shepherd-user-file-systems.scm.drv
  
/gnu/store/1blrbcbd54yxzc6i57gqba3wf59icc6p-shepherd-file-system--sys-kernel-debug.go.drv
  
/gnu/store/69i8aqkgqlka4f9ld1dg6bqgykc6ygpa-shepherd-file-system--sys-kernel-debug.scm.drv
  /gnu/store/1sriznlp88pvsjl7nc0pjjzbdy5ws3af-shepherd-loopback.go.drv
  /gnu/store/rrxcn31zcsnxlaq8zk9gll4iidh0ic1m-shepherd-loopback.scm.drv
  /gnu/store/v31z2xn1cppj0a1f3yiyvj644vmwndin-set-up-network.drv
  /gnu/store/y6jhmhhi82pmbdajj69bbzmy4k32pdfg-tear-down-network.drv
  /gnu/store/2kk9i32m2kb8cnz30j4bwh4mmdndppl5-shepherd-term-tty4.go.drv
  /gnu/store/k05d8mgivw164n2y4gjg2x3z7lkqdpqw-shepherd-term-tty4.scm.drv
  /gnu/store/520k2gmf1ijjb76ya5w6ygbv4liwp39k-shepherd-sysctl.go.drv
  /gnu/store/fib3qy0y43a4a93qyndqbikvqgrhfkxa-shepherd-sysctl.scm.drv
  
/gnu/store/7s3s1668iaiim9dpgz1a7csff4jwc3xh-shepherd-file-system--gnu-store.go.drv
  

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[Josselin Poiret via Bug reports for GNU Guix]

Hi dan,

dan  writes:

> with git bisect i found after this commit the cross-compilation 
> couldn't work anymore:

Could you post some more details about what you mean by "couldn't work"?
What exactly is failing, and with what logs?

Best,
-- 
Josselin Poiret


signature.asc
Description: PGP signature

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[dan]

with git bisect i found after this commit the cross-compilation 
couldn't work anymore:

http://git.savannah.gnu.org/cgit/guix.git/commit/?id=1328c4cca531318e3ed90c6aecb522a5b22a4bcc

i think this is beyond my ability to understand why it breaks, but 
if anyone could take a look at this it would be really helpful.

--
dan

bug#66866: aarch64 system cross compilation + pinebook pro image broken?

[Denis 'GNUtoo' Carikli]

Hi,

With:
> $ guix describe
> Generation 311nov. 01 2023 00:03:34   (current)
>   guix 938a47c
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: 938a47c86d7bea785f33f42834c5c1f3dfa594b0

And the following minimalist system configuration:
> ;;; Copyright © 2023 Denis 'GNUtoo' Carikli. SPDX-License-Identifier:
> GPL-3.0+ (use-modules (gnu bootloader) 
>(gnu bootloader u-boot)
>(gnu system file-systems)
>(gnu packages linux)
>(guix gexp))
> (operating-system
>   (host-name "g")
>   (bootloader (bootloader-configuration
>   (bootloader u-boot-rockpro64-rk3399-bootloader)
>   (targets '("/dev/mmcblk2"
>   (kernel linux-libre-arm64-generic)
>   (file-systems (cons (file-system (mount-point "/")
>(device "/dev/vda1")
>(type "ext4"))
>%base-file-systems)))

that I built with:
> guix system build --target=aarch64-linux-gnu noconfig.scm

I end up with:
> [...]
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... Invalid configuration
> `aarch64-linux-gnu': machine `aarch64' not recognized configure:
> error:
> /gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash
> ./config.sub aarch64-linux-gnu failed error: in phase 'configure':
> uncaught exception: srfi-34 # "/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash"
> arguments: ("./configure" "CC_FOR_BUILD=gcc"
> "CONFIG_SHELL=/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash"
> "SHELL=/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash"
> "--prefix=/gnu/store/mn43k8aldd7h9jcx8q5ryij29kdqriz0-gawk-mesboot-3.1.8"
> "--enable-fast-install" "--build=x86_64-unknown-linux-gnu"
> "--host=aarch64-linux-gnu" "ac_cv_func_connect=no") exit-status: 1
> term-signal: #f stop-signal: #f] 1700400> phase `configure' failed
> after 115.3 seconds command
> "/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash"
> "./configure" "CC_FOR_BUILD=gcc"
> "CONFIG_SHELL=/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash"
> "SHELL=/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash"
> "--prefix=/gnu/store/mn43k8aldd7h9jcx8q5ryij29kdqriz0-gawk-mesboot-3.1.8"
> "--enable-fast-install" "--build=x86_64-unknown-linux-gnu"
> "--host=aarch64-linux-gnu" "ac_cv_func_connect=no" failed with status
> 1 builder for
> `/gnu/store/9xwp6pi7ssi9jhhj50dd1apryidcz2hk-gawk-mesboot-3.1.8.drv'
> failed with exit code 1 build of
> /gnu/store/9xwp6pi7ssi9jhhj50dd1apryidcz2hk-gawk-mesboot-3.1.8.drv
> failed View build log at
> '/var/log/guix/drvs/9x/wp6pi7ssi9jhhj50dd1apryidcz2hk-gawk-mesboot-3.1.8.drv.gz'.
> cannot build derivation
> `/gnu/store/jgd1kl2zavkxsvxa875r8lpndq292vgb-glibc-2.35.drv': 1
> dependencies couldn't be built guix system: error: build of
> `/gnu/store/jgd1kl2zavkxsvxa875r8lpndq292vgb-glibc-2.35.drv' failed

I've tried to bisect that with:
$ guix time-machine --commit= -- \
  system build--target=aarch64-linux-gnu noconfig.scm 
but strangely I failed to find some working commit, so I end up not
being able to bisect.

As I understand the Pinebook pro image is also cross compiled, so
normally that should fail in the same way. But here something is
really strange as well:
- The CI says everything is ok here:
  https://ci.guix.gnu.org/build/2279759/details
- The download image doesn't exist but return '{"error":"Could not find
  the requested build product."}' instead.

That correspond to the commit e6af40d7b46b5c9e397a38c62c885fb42ccd9d26 .

So if I use:
> ;; Adapted from Guix manual, GFDL 1.3 (+?)
> (use-modules (gnu system images pine64))
> (operating-system (inherit pine64-barebones-os))

with:
$ guix time-machine \
  --commit=e6af40d7b46b5c9e397a38c62c885fb42ccd9d26 \
  -- \
  system build --target=aarch64-linux-gnu pine64.scm 

I still end up with:
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... Invalid configuration
> `aarch64-linux-gnu': machine `aarch64' not recognized configure:
> error:
> /gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash
> ./config.sub aarch64-linux-gnu failed error: in phase 'configure':
> uncaught exception: srfi-34 # "/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash"
> arguments: ("./configure" "CC_FOR_BUILD=gcc"
> "CONFIG_SHELL=/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash"
> "SHELL=/gnu/store/rb75igdc6daly1mz2ivz7rs8hd85imdz-gash-boot-0.3.0/bin/bash"
> "--prefix=/gnu/store/mn43k8aldd7h9jcx8q5ryij29kdqriz0-gawk-mesboot-3.1.8"
> "--enable-fast-install" "--build=x86_64-unknown-linux-gnu"
> "--host=aarch64-linux-gnu" "ac_cv_func_connect=no") exit-status: 1
> term-signal: #f stop-signal: #f] 170f400> phase `configure' failed
> after 209.2 seconds command
>