GNU bug report logs - #74797
linux-libre 6.11.11 fails to build on aarch64 (drivers/clk/meson/gxbb.c)

Previous Next

Package: guix;

Reported by: Vagrant Cascadian <vagrant <at> debian.org>

Date: Wed, 11 Dec 2024 18:37:01 UTC

Severity: normal

Done: Vagrant Cascadian <vagrant <at> debian.org>

Bug is archived. No further changes may be made.

Full log


Message #16 received at 74797-done <at> debbugs.gnu.org (full text, mbox):

From: Vagrant Cascadian <vagrant <at> debian.org>
To: Vincent Legoll <vincent.legoll <at> gmail.com>, 74797-done <at> debbugs.gnu.org
Cc: Wilko Meyer <w <at> wmeyer.eu>, Maxim Cournoyer <maxim.cournoyer <at> gmail.com>,
 Leo Famulari <leo <at> famulari.name>
Subject: Re: bug#74797 - Re: linux-libre 6.11.11 fails to build on aarch64
 (drivers/clk/meson/gxbb.c)
Date: Fri, 13 Dec 2024 23:56:35 -0800
[Message part 1 (text/plain, inline)]
On 2024-12-12, Vincent Legoll wrote:
> that file looks corrupted
>
> For example the first error:
>
> 2057 |         .hw.init = &(struct clk_init_da|a) {
>
> that should be "clk_init_data", see:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/clk/meson/gxbb.c#n2051
>
> 2168 |                 .parent_hws = (const str}ct clk_hw *[]) {
>
> here it's "struct"

You are right! Somehow the source tarballs had gotten corrupted.

When I tried to untar one of the tarballs manually, it was so corrupted
that it failed to unpack it, which makes me wonder how it actually got
as far as trying to build the kernel...

I 'guix gc'ed them and was able to successfully build after a few tries
and freeing up more and more disk space.

The worried part of me wonders if there is bad hardware, ram, disk or
cpu...

But seems to be working for now!

live well,
  vagrant
[signature.asc (application/pgp-signature, inline)]

This bug report was last modified 209 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.