public inbox for nightly-builds@lists.ipfire.org
 help / color / mirror / Atom feed
From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (2d0b52b) for aarch64 on arm64-01.zrh.ipfire.org
Date: Fri, 24 May 2024 10:06:00 +0000	[thread overview]
Message-ID: <4Vm0zr39NHz1y5V@arm64-01.zrh.ipfire.org> (raw)

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

https://nightly.ipfire.org/next/2024-05-24%2007%3A20%3A12%20%2B0200-2d0b52b9/aarch64

commit 2d0b52b932d6738a7be84f94d84927bf82de0768
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Fri May 24 07:20:12 2024 +0200

    core187: ship gcc
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=2d0b52b932d6738a7be84f94d84927bf82de0768

Packaged toolchain compilation                                          
Checking for necessary space on disk                                    [ DONE ]
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
mount: (hint) your fstab has been modified, but systemd still uses
       the old version; use 'systemctl daemon-reload' to reload.
Set cache size limit to 4.0 GB
Building LFS                                                            
stage2                                                      [        1 ][ DONE ]
linux (6.6.31)                                KCFG=-headers [       23 ][ DONE ]
man-pages (5.13)                                            [        7 ][ DONE ]
glibc (2.39)                                                

             reply	other threads:[~2024-05-24 10:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 10:06 IPFire Nightly Builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-24 10:02 IPFire Nightly Builder

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=4Vm0zr39NHz1y5V@arm64-01.zrh.ipfire.org \
    --to=nightly-builds@ipfire.org \
    --cc=nightly-builds@lists.ipfire.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox