From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (93f83a3) for armv5tel on arm64-02.dub.ipfire.org
Date: Sat, 17 Jul 2021 02:36:05 +0000 [thread overview]
Message-ID: <4GRXKd6rWsz602d@arm64-02.dub.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
https://nightly.ipfire.org/next/2021-07-15%2022%3A41%3A51%20%2B0200-93f83a3f/armv5tel
commit 93f83a3f0d7ecaed22675bb47f33c74dc994b52b
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Jul 15 22:41:51 2021 +0200
kernel: update to 5.10.50
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=93f83a3f0d7ecaed22675bb47f33c74dc994b52b
ERROR: Cannot build for architure armv5tel [ FAIL ]
Check /build/nightly/next/log/_build.preparation.log for errors if applicable[ FAIL ]
next reply other threads:[~2021-07-17 2:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-17 2:36 IPFire Nightly Builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-19 13:57 IPFire Nightly Builder
2021-07-19 8:50 IPFire Nightly Builder
2021-07-19 3:56 IPFire Nightly Builder
2021-07-18 22:57 IPFire Nightly Builder
2021-07-18 18:37 IPFire Nightly Builder
2021-07-18 14:48 IPFire Nightly Builder
2021-07-18 10:38 IPFire Nightly Builder
2021-07-18 6:36 IPFire Nightly Builder
2021-07-18 2:51 IPFire Nightly Builder
2021-07-17 22:36 IPFire Nightly Builder
2021-07-17 18:36 IPFire Nightly Builder
2021-07-17 14:34 IPFire Nightly Builder
2021-07-17 10:35 IPFire Nightly Builder
2021-07-17 6:36 IPFire Nightly Builder
2021-07-16 22:38 IPFire Nightly Builder
2021-07-16 18:39 IPFire Nightly Builder
2021-07-16 14:57 IPFire Nightly Builder
2021-07-16 10:43 IPFire Nightly Builder
2021-07-16 6:44 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=4GRXKd6rWsz602d@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