[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdUHG-4=HEOspGH=-6P_nTdbR_wYnyKdyUR9+-2=r1fNkQ@mail.gmail.com>
Date: Wed, 2 Oct 2019 11:17:26 +0200
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc: linux-mips@...r.kernel.org, Matthew Wilcox <willy@...radead.org>,
Arnd Bergmann <arnd@...db.de>,
David Daney <ddaney.cavm@...il.com>,
Alex Vesker <valex@...lanox.com>,
Matt Fleming <matt@...eblueprint.co.uk>
Subject: Re: Build regressions/improvements in v5.4-rc1
On Wed, Oct 2, 2019 at 11:05 AM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
> Below is the list of build error/warning regressions/improvements in
> v5.4-rc1[1] compared to v5.3[2].
>
> Summarized:
> - build errors: +15/-3
> - build warnings: +215/-117
>
> Note that there may be false regressions, as some logs are incomplete.
> Still, they're build errors/warnings.
>
> Happy fixing! ;-)
>
> Thanks to the linux-next team for providing the build service.
>
> [1] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/54ecb8f7028c5eb3d740bb82b0f1d90f2df63c5c/ (233 out of 242 configs)
> [2] http://kisskb.ellerman.id.au/kisskb/branch/linus/head/4d856f72c10ecb060868ed10ff1b1453943fc6c8/ (all 242 configs)
>
>
> *** ERRORS ***
>
> 15 error regressions:
> + /kisskb/build/tmp/cc1Or5dj.s: Error: can't resolve `_start' {*UND* section} - `L0 ' {.text section}: => 663, 1200, 222, 873, 1420
> + /kisskb/build/tmp/cc2uWmof.s: Error: can't resolve `_start' {*UND* section} - `L0 ' {.text section}: => 1213, 919, 688, 1434, 226
> + /kisskb/build/tmp/ccc6hBqd.s: Error: can't resolve `_start' {*UND* section} - `L0 ' {.text section}: => 513, 1279, 1058, 727
> + /kisskb/build/tmp/cclSQ19p.s: Error: can't resolve `_start' {*UND* section} - `L0 ' {.text section}: => 1396, 881, 1175, 671, 226
> + /kisskb/build/tmp/ccu3SlxY.s: Error: can't resolve `_start' {*UND* section} - `L0 ' {.text section}: => 1238, 911, 222, 680, 1457
Various mips (allmodconfig, allnoconfig, malta_defconfig, ip22_defconfig)
Related to
/kisskb/src/arch/mips/vdso/Makefile:61: MIPS VDSO requires binutils >= 2.25
?
> + /kisskb/src/arch/mips/include/asm/octeon/cvmx-ipd.h: error: 'CVMX_PIP_SFT_RST' undeclared (first use in this function): => 331:36
> + /kisskb/src/arch/mips/include/asm/octeon/cvmx-ipd.h: error: 'CVMX_PIP_SFT_RST' undeclared (first use in this function); did you mean 'CVMX_CIU_SOFT_RST'?: => 331:36
> + /kisskb/src/arch/mips/include/asm/octeon/cvmx-ipd.h: error: storage size of 'pip_sft_rst' isn't known: => 330:27
mips-allmodconfig (CC Matthew Wilcox)
> + /kisskb/src/drivers/watchdog/cpwd.c: error: 'compat_ptr_ioctl' undeclared here (not in a function): => 500:19
sparc64-allmodconfig (CC Arnd Bergmann)
> + error: "__delay" [drivers/net/phy/mdio-cavium.ko] undefined!: => N/A
sh-allmodconfig (CC David Daney)
> + error: "__moddi3" [drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.ko] undefined!: => N/A
> + error: "__umoddi3" [drivers/net/ethernet/mellanox/mlx5/core/mlx5_core.ko] undefined!: => N/A
parisc-allmodconfig (CC Alex Vesker)
> + error: c2p_iplan2.c: undefined reference to `c2p_unsupported': => .text+0xc4), .text+0x150)
> + error: c2p_planar.c: undefined reference to `c2p_unsupported': => .text+0xd6), .text+0x1dc)
m68k-defconfig (https://lore.kernel.org/lkml/20190927094708.11563-1-geert@linux-m68k.org/)
> + error: page_alloc.c: undefined reference to `node_reclaim_distance': => .text+0x3180), .text+0x3148)
Various sh4 (migor_defconfig, se7722_defconfig, ul2_defconfig) (CC Matt Fleming)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists