all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Vincent Legoll <vincent.legoll@gmail.com>, 74797-done@debbugs.gnu.org
Cc: Wilko Meyer <w@wmeyer.eu>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>,
	Leo Famulari <leo@famulari.name>
Subject: 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	[thread overview]
Message-ID: <87a5cyu28c.fsf@wireframe> (raw)
In-Reply-To: <CAEwRq=pOMJxDhn=LZX5e3ss5=W9o7usS_8mTruMdRWn2H1NtRw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2024-12-14  7:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 18:36 bug#74797: linux-libre 6.11.11 fails to build on aarch64 (drivers/clk/meson/gxbb.c) Vagrant Cascadian
2024-12-12  8:37 ` bug#74797: - " Vincent Legoll
2024-12-14  7:15   ` bug#74797: " Maxim Cournoyer
2024-12-14  7:56   ` Vagrant Cascadian [this message]
2024-12-14 11:12     ` bug#74797: - " Vincent Legoll

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a5cyu28c.fsf@wireframe \
    --to=vagrant@debian.org \
    --cc=74797-done@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=maxim.cournoyer@gmail.com \
    --cc=vincent.legoll@gmail.com \
    --cc=w@wmeyer.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.