[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240702091614.2334b182@canb.auug.org.au>
Date: Tue, 2 Jul 2024 09:16:14 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Mirsad Todorovac <mtodorovac69@...il.com>, Mark Brown
<broonie@...nel.org>, Linux Kernel Build System
<linux-kbuild@...r.kernel.org>, Linux Kernel Mailing List
<linux-kernel@...r.kernel.org>, Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>, linux-arm-msm@...r.kernel.org
Subject: Re: [PROBLEM linux-next] ERROR: modpost: "devm_qcom_tzmem_pool_new"
[drivers/firmware/qcom/qcom-scm.ko] undefined!
Hi Bart,
On Mon, 1 Jul 2024 09:33:47 +0200 Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> On Fri, Jun 28, 2024 at 8:27 PM Mirsad Todorovac <mtodorovac69@...il.com> wrote:
> >
> > In vanilla linux-next next-20240627 branch, there seems to be a build error with
> > KCONFIG_SEED=0x44AB31A6.
> >
> > The error log is:
> >
> > ~/linux/kernel/linux-next$ time nice make -j 36 bindeb-pkg |& tee ../err-6.10-rc5-next-20240627-29.log; date
> > GEN debian
> > dpkg-buildpackage --build=binary --no-pre-clean --unsigned-changes -R'make -f debian/rules' -j1 -a$(cat debian/arch)
> > dpkg-buildpackage: info: source package linux-upstream
> > dpkg-buildpackage: info: source version 6.10.0-rc5-38
> > dpkg-buildpackage: info: source distribution jammy
> > dpkg-buildpackage: info: source changed by marvin <marvin@...iant>
> > dpkg-source --before-build .
> > dpkg-buildpackage: info: host architecture amd64
> > make -f debian/rules binary
> > #
> > # No change to .config
> > #
> > mkdir -p /home/marvin/linux/kernel/linux-next/tools/objtool && make O=/home/marvin/linux/kernel/linux-next subdir=tools/objtool --no-print-directory -C objtool
> > mkdir -p /home/marvin/linux/kernel/linux-next/tools/bpf/resolve_btfids && make O=/home/marvin/linux/kernel/linux-next subdir=tools/bpf/resolve_btfids --no-print-directory -C bpf/resolve_btfids
> > INSTALL libsubcmd_headers
> > INSTALL libsubcmd_headers
> > CALL scripts/checksyscalls.sh
> > UPD init/utsversion-tmp.h
> > CC init/version.o
> > AR init/built-in.a
> > CHK kernel/kheaders_data.tar.xz
> > AR built-in.a
> > AR vmlinux.a
> > LD vmlinux.o
> > OBJCOPY modules.builtin.modinfo
> > GEN modules.builtin
> > MODPOST Module.symvers
> > ERROR: modpost: "devm_qcom_tzmem_pool_new" [drivers/firmware/qcom/qcom-scm.ko] undefined!
> > make[5]: *** [scripts/Makefile.modpost:145: Module.symvers] Error 1
> > make[4]: *** [Makefile:1886: modpost] Error 2
> > make[3]: *** [debian/rules:74: build-arch] Error 2
> > dpkg-buildpackage: error: make -f debian/rules binary subprocess returned exit status 2
> > make[2]: *** [scripts/Makefile.package:121: bindeb-pkg] Error 2
> > make[1]: *** [/home/marvin/linux/kernel/linux-next/Makefile:1555: bindeb-pkg] Error 2
> > make: *** [Makefile:240: __sub-make] Error 2
> >
> > real 0m5.950s
> > user 0m15.971s
> > sys 0m10.430s
> > Fri Jun 28 20:22:03 CEST 2024
> > ~/linux/kernel/linux-next$
> >
> > Please find attached .config, just to be sure that we are talking about the same thing.
> >
> > Best regards,
> > Mirsad Todorovac
>
> The fix for this is in the qcom tree[1] but I'm not sure why it still
> hasn't been pulled into next. I don't see any notifications about
> conflicts in next which could be the reason. Cc'ing Mark and Stephen.
>
> Bart
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/commit/?h=for-next&id=d96377892dd89bd4e7e5ae7293647f6bc7bddf7d
The qcom tree has another build failure and so new versions of it have
not been merged into linux-next since June 24. Hopefully today the
other build failure will be fixed.
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists