stable-rc: 5.15: arm: fsl_dcu_drm_plane.c:176:20: error: 'drm_plane_helper_destroy' undeclared here
While building Linux stable rc 5.15 arm with gcc-13 failed due to following warnings / errors.
make --silent --keep-going --jobs=8 O=/home/tuxbuild/.cache/tuxmake/builds/1/build ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- 'CC=sccache arm-linux-gnueabihf-gcc' 'HOSTCC=sccache gcc' drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.c:176:20: error: 'drm_plane_helper_destroy' undeclared here (not in a function); did you mean 'drm_primary_helper_destroy'? 176 | .destroy = drm_plane_helper_destroy, | ^~~~~~~~~~~~~~~~~~~~~~~~ | drm_primary_helper_destroy make[5]: *** [scripts/Makefile.build:289: drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.o] Error 1 make[5]: Target '__build' not remade because of errors. make[4]: *** [scripts/Makefile.build:552: drivers/gpu/drm/fsl-dcu] Error 2 drivers/firmware/arm_scmi/smc.c:39:13: error: duplicate member 'irq' 39 | int irq; | ^~~ drivers/firmware/arm_scmi/smc.c: In function 'smc_chan_setup': drivers/firmware/arm_scmi/smc.c:118:34: error: 'irq' undeclared (first use in this function); did you mean 'rq'? 118 | scmi_info->irq = irq; | ^~~ | rq drivers/firmware/arm_scmi/smc.c:118:34: note: each undeclared identifier is reported only once for each function it appears in make[4]: *** [scripts/Makefile.build:289: drivers/firmware/arm_scmi/smc.o] Error 1
Build links, - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15.... - https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.15.y/build/v5.15.... - https://storage.tuxsuite.com/public/linaro/lkft/builds/2TiTIjkQ8vGDk4J7tsucF...
Steps to reproduce: tuxmake --runtime podman --target-arch arm --toolchain gcc-13 --kconfig https://storage.tuxsuite.com/public/linaro/lkft/builds/2TiTIjkQ8vGDk4J7tsucF... https://storage.tuxsuite.com/public/linaro/lkft/builds/2TiTIjkQ8vGDk4J7tsucF...
-- Linaro LKFT https://lkft.linaro.org
On Wed, Aug 09, 2023 at 11:47:45AM +0530, Naresh Kamboju wrote:
While building Linux stable rc 5.15 arm with gcc-13 failed due to following warnings / errors.
I appreciate you attempting to build older LTS trees with newer compilers, but note that usually, as you are finding out, this doesn't work.
Right now I've finally gotten support for gcc-12 in all active stable kernel trees, gcc-13 takes more work as you are finding out so I'm only testing with newer trees (6.1 and newer).
So when you run into issues like this, that obviously work in newer kernel releases, a report doesn't do much, BUT a git commit id of what the commit that needs to be backported IS appreciated.
thanks,
greg k-h
On Wed, 9 Aug 2023 at 12:29, Greg Kroah-Hartman gregkh@linuxfoundation.org wrote:
On Wed, Aug 09, 2023 at 11:47:45AM +0530, Naresh Kamboju wrote:
While building Linux stable rc 5.15 arm with gcc-13 failed due to following warnings / errors.
I appreciate you attempting to build older LTS trees with newer compilers, but note that usually, as you are finding out, this doesn't work.
These reports make us aware that we have found new issues with newer tool chains on older LTS trees / branches.
Right now I've finally gotten support for gcc-12 in all active stable kernel trees, gcc-13 takes more work as you are finding out so I'm only testing with newer trees (6.1 and newer).
We have seen great work (fixes) for gcc-12 when it got released. I think I / We should not expect this with gcc-13 since it takes more work.
As I understand, stable-rc 6.1 testing with gcc-13 would be ok. other than stable-rc 6.1 branches 5.x and 4.x should be built with gcc-12.
So when you run into issues like this, that obviously work in newer kernel releases, a report doesn't do much, BUT a git commit id of what the commit that needs to be backported IS appreciated.
Thanks for explaining the details here. If I come across any fixed patch / commit id then I will share that information.
thanks,
greg k-h
thanks, Naresh Kamboju
-
Greg Kroah-Hartman -
Naresh Kamboju