From: Pavel Machek <pavel@denx.de>
To: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
Cc: "pavel@denx.de" <pavel@denx.de>,
"alice.ferrazzi@miraclelinux.com"
<alice.ferrazzi@miraclelinux.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>,
"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: [cip-dev] cip/linux-4.4.y-cip build: 187 builds: 5 failed, 182 passed, 6 errors, 200 warnings (v4.4.302-cip69-508-gd887d54a1be6) #kernelci
Date: Sat, 16 Jul 2022 12:49:56 +0200 [thread overview]
Message-ID: <20220716104956.GA18467@duo.ucw.cz> (raw)
In-Reply-To: <3a28a0046f2dbc660d2771617e81c08b60236f2f.camel@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 2044 bytes --]
Hi!
> > cip/linux-4.4.y-cip build: 187 builds: 5 failed, 182 passed, 6 errors, 200 warnings (v4.4.302-cip69-508-gd887d54a1be6)
> >
> > Full Build Summary: https://kernelci.org/build/cip/branch/linux-4.4.y-cip/kernel/v4.4.302-cip69-508-gd887d54a1be6/
> >
> > Tree: cip
> > Branch: linux-4.4.y-cip
> > Git Describe: v4.4.302-cip69-508-gd887d54a1be6
> > Git Commit: d887d54a1be6de9a74cb732ba80ecaf1cedefb61
> > Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
> > Built: 6 unique architectures
> >
> > Build Failures Detected:
> >
> > arm:
> > rpc_defconfig: (gcc-10) FAIL
>
> The log tells me:
>
> arm-linux-gnueabihf-gcc: error: unrecognized -march target: armv3
> arm-linux-gnueabihf-gcc: error: missing argument to ‘-march=’
>
> AFAIK armv3 support has been removed from gcc 9, we're using gcc 10
> here. If we still care about such boards we would have to switch to a
> older compiler (for that config). Don't know yet if that is possible in
> kernelci configuration.
I'm not sure what machine "rpc" is. It is quite probable it does not
really need armv3 instruction set.
>
> > mips:
> > fuloong2e_defconfig: (gcc-10) FAIL
> > ip27_defconfig: (gcc-10) FAIL
> > ip28_defconfig: (gcc-10) FAIL
> > lemote2f_defconfig: (gcc-10) FAIL
>
> According to [1] CIP does not have a single mips reference board, so I
> assume we could simply skip mips completely, right?
>
> Should we disable mips unconditionally for all branches, or just for
> 4.4. because it makes problems here? I would vote for 4.4 disablement
> only, but no idea if we can configure that in kernelci configuration.
> Let's see...
We could. Even better would be running 4.4-stable with same configs,
and see if they fail, too. If -stable works and -cip fails, we might
want to look into that.
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2022-07-16 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 12:56 cip/linux-4.4.y-cip build: 187 builds: 5 failed, 182 passed, 6 errors, 200 warnings (v4.4.302-cip69-508-gd887d54a1be6) kernelci.org bot
2022-07-14 15:40 ` [cip-dev] cip/linux-4.4.y-cip build: 187 builds: 5 failed, 182 passed, 6 errors, 200 warnings (v4.4.302-cip69-508-gd887d54a1be6) #kernelci Bezdeka, Florian
2022-07-16 10:49 ` Pavel Machek [this message]
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=20220716104956.GA18467@duo.ucw.cz \
--to=pavel@denx.de \
--cc=alice.ferrazzi@miraclelinux.com \
--cc=cip-dev@lists.cip-project.org \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
/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