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 (bcea571) for armv5tel on arm64-02.dub.ipfire.org
Date: Wed, 28 Jul 2021 22:05:21 +0000	[thread overview]
Message-ID: <4GZnlj6dHsz604w@arm64-02.dub.ipfire.org> (raw)

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

https://nightly.ipfire.org/next/2021-07-25%2023%3A48%3A58%20%2B0200-bcea5712/armv5tel

commit bcea5712116c173ff2b8a414f076414c1b74a919
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sun Jul 25 23:48:58 2021 +0200

    kernel: update to 5.10.53
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

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


ERROR: Cannot build for architure armv5tel                              [ FAIL ]
    Check /build/nightly/next/log/_build.preparation.log for errors if applicable[ FAIL ]

             reply	other threads:[~2021-07-28 22:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 22:05 IPFire Nightly Builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-07-28 17:02 IPFire Nightly Builder
2021-07-28 11:59 IPFire Nightly Builder
2021-07-28  6:50 IPFire Nightly Builder
2021-07-28  1:38 IPFire Nightly Builder
2021-07-27 20:33 IPFire Nightly Builder
2021-07-27 15:28 IPFire Nightly Builder
2021-07-27 10:14 IPFire Nightly Builder
2021-07-27  5:10 IPFire Nightly Builder
2021-07-27  0:07 IPFire Nightly Builder
2021-07-26 19:06 IPFire Nightly Builder
2021-07-26 14:06 IPFire Nightly Builder
2021-07-26  8:56 IPFire Nightly Builder
2021-07-26  4:54 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=4GZnlj6dHsz604w@arm64-02.dub.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