From: Heiko Carstens <hca@linux.ibm.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
Alexey Gladkov <legion@kernel.org>,
linux-s390@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
Arnd Bergmann <arnd@arndb.de>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>,
Ben Copeland <benjamin.copeland@linaro.org>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Subject: Re: next-20251002: S390: gcc-8-defconfig: symbol `.modinfo' required but not present - no symbols
Date: Wed, 8 Oct 2025 13:33:34 +0200 [thread overview]
Message-ID: <20251008113334.7407C2a-hca@linux.ibm.com> (raw)
In-Reply-To: <20251008031849.GA509861@ax162>
Hi Nathan,
On Tue, Oct 07, 2025 at 08:18:49PM -0700, Nathan Chancellor wrote:
> On Mon, Oct 06, 2025 at 04:41:19PM -0700, Nathan Chancellor wrote:
> ...
> > > > ### Build error log
> > > > s390x-linux-gnu-ld: .tmp_vmlinux1: warning: allocated section `.got.plt' not in segment
> > > > s390x-linux-gnu-ld: .tmp_vmlinux2: warning: allocated section `.got.plt' not in segment
> > > > s390x-linux-gnu-ld: vmlinux.unstripped: warning: allocated section `.got.plt' not in segment
> > > > s390x-linux-gnu-objcopy: vmlinux: warning: allocated section `.got.plt' not in segment
> > > > s390x-linux-gnu-objcopy: stM7JmYX: warning: allocated section `.got.plt' not in segment
>
> So these warnings should be fixed with:
...
> I am unsure why newer binutils does not show this but I did not care
> enough to actually bisect.
>
> > > > s390x-linux-gnu-objcopy: stM7JmYX: symbol `.modinfo' required but not present
> > > > s390x-linux-gnu-objcopy:stM7JmYX: no symbols
>
> I did bisect binutils to figure out that commit c12d9fa2afe ("Support
> objcopy --remove-section=.relaFOO") [1] in binutils 2.32 resolves this
> error.
>
> I can fix this for those older binutils with:
>
> diff --git a/scripts/Makefile.vmlinux b/scripts/Makefile.vmlinux
> index 7c6ae9886f8f..9ea92c3317dc 100644
> --- a/scripts/Makefile.vmlinux
> +++ b/scripts/Makefile.vmlinux
> @@ -82,7 +82,7 @@ endif
> # ---------------------------------------------------------------------------
>
> remove-section-y := .modinfo
> -remove-section-$(CONFIG_ARCH_VMLINUX_NEEDS_RELOCS) += '.rel*'
> +remove-section-$(CONFIG_ARCH_VMLINUX_NEEDS_RELOCS) += '.rel*' '.rel.*'
>
> remove-symbols := -w --strip-symbol='__mod_device_table__*'
>
> I can send a patch series tomorrow.
Thank you for figuring this out. Highly appreciated!
prev parent reply other threads:[~2025-10-08 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 11:25 next-20251002: S390: gcc-8-defconfig: symbol `.modinfo' required but not present - no symbols Naresh Kamboju
2025-10-06 17:47 ` Heiko Carstens
2025-10-06 23:41 ` Nathan Chancellor
2025-10-08 3:18 ` Nathan Chancellor
2025-10-08 11:33 ` Heiko Carstens [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=20251008113334.7407C2a-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=gor@linux.ibm.com \
--cc=legion@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).