Ludovic Courtès <ludo@gnu.org> writes:

Hello,

I tried the core-updates on an Apple M1 aarch64 and can't build
libcamera. I sent a patch (bug#69178) that fixes this a while ago.

This is the log from the failing tests:

```
53/70 libcamera / file                                           FAIL            0.01s   (exit status 255 or signal 127 SIGinvalid)
>>> MALLOC_PERTURB_=33 LD_LIBRARY_PATH=/tmp/guix-build-libcamera-0.1.0.drv-0/build/src/libcamera:/tmp/guix-build-libcamera-0.1.0.drv-0/build/src/libcamera/base /tmp/guix-build-libcamera-0.1.0.drv-0/build/test/file
――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
stderr:
Mapping of file region failed
――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――

54/70 libcamera / flags                                          OK              0.00s
55/70 libcamera / hotplug-cameras                                SKIP            0.01s   exit status 77
56/70 libcamera / message                                        OK              0.23s
57/70 libcamera / object                                         OK              0.01s
58/70 libcamera / object-delete                                  OK              0.01s
59/70 libcamera / object-invoke                                  OK              0.01s
60/70 libcamera / pixel-format                                   OK              0.01s
61/70 libcamera / shared-fd                                      OK              0.01s
62/70 libcamera / signal-threads                                 OK              0.11s
63/70 libcamera / threads                                        OK              0.51s
64/70 libcamera / timer                                          OK              8.66s
65/70 libcamera / timer-thread                                   OK              0.41s
66/70 libcamera / unique-fd                                      OK              0.01s
67/70 libcamera / utils                                          OK              0.01s
68/70 libcamera / yaml-parser                                    OK              0.01s
69/70 libcamera / fence                                          SKIP            0.01s   exit status 77
70/70 libcamera / mapped-buffer                                  SKIP            0.01s   exit status 77

Summary of Failures:

53/70 libcamera / file                                           FAIL            0.01s   (exit status 255 or signal 127 SIGinvalid)

Ok:                 35  
Expected Fail:      0   
Fail:               1   
Unexpected Pass:    0   
Skipped:            34  
Timeout:            0   
```

Could we please include this patch?

Thanks, Roman.

> Hello Guix!
>
> I’d like to propose merging ‘core-updates’ real soon, say by next week,
> Friday 30th.
>
>
> But first, this branch started about a year ago (!), and it’s hard for
> someone who’s not following IRC 7 days a week to figure out what the
> status is—something we should definitely improve on.
>
> An overview in terms of package coverage can be found here:
>
>   https://qa.guix.gnu.org/branch/core-updates
>
> To view “blocking builds” (packages that fail to build and thus “block”
> all those that depend on it), say for i686-linux, see:
>
>   https://data.qa.guix.gnu.org/revision/aab1fe98574e1cd4c7911c1e5571b3733fb71d67/blocking-builds?system=i686-linux&target=none&limit_results=50
>
> or run:
>
>   ./pre-inst-env guix weather -s i686-linux -c 200
>
> from a ‘core-updates’ checkout.  This gives an idea where to focus our
> efforts.  You can also browse individual ci.guix builds at:
>
>   https://ci.guix.gnu.org/eval/latest/dashboard?spec=core-updates
>
> Currently, we’re at ~95% on x86_64-linux, 80–90% on the other *-linux
> systems, and ~2% on i586-gnu (GNU/Hurd; that’s more or less where we
> were before.)  Note that ci.guix is still struggling with aarch64-linux
> build and hasn’t even attempted armhf-linux builds, but bordeaux.guix is
> doing well.
>
> I’m aware of at least one important issue that prevents use of Guix
> System on i686-linux:
>
>   https://issues.guix.gnu.org/72725
>
> To me, that’s the last blocker, even though there’s room for improvement
> here and there (for instance, FFmpeg currently fails to build on
> i686-linux).
>
> Anything else?
>
>
> A number of people already provided feedback informally after
> reconfiguring their systems on ‘core-updates’.  Please share your
> experience, positive or negative, here!
>
> Ludo’.