Re: cip/linux-4.4.y-cip build: 187 builds: 5 failed, 182 passed, 6 errors, 200 warnings (v4.4.302-cip69-508-gd887d54a1be6) #kernelci


Pavel Machek
 

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

Join cip-dev@lists.cip-project.org to automatically receive all group messages.