From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: Possible regression due to 269a535ca931 "modpost: generate vmlinux.symvers and reuse it for the second modpost"
Date: Fri, 5 Mar 2021 14:15:46 +0000 [thread overview]
Message-ID: <985bf10d-336c-61f6-8b9d-d8c6fb48634a@arm.com> (raw)
In-Reply-To: <CAK7LNASX-Rx_fxcuqQ_vFHQwQ+RJq9XCW9_dL=jFCuoEJ0vF3Q@mail.gmail.com>
On 3/4/21 5:24 PM, Masahiro Yamada wrote:
> On Fri, Mar 5, 2021 at 1:21 AM Vladimir Murzin <vladimir.murzin@arm.com> wrote:
> [ snip long description ]
>
>>
>> Does that make sense? What I'm missing?
>>
>> P.S.
>> I've also checked v5.12-rc1 and see the same symptoms
>
> Since you ran "make allnoconfig",
> the module feature was disabled.
> (CONFIG_MODULES=n)
>
> That is why you cannot build external modules.
That's a good point, yet was not reason for my issue :) It forced me to try with ARCH=arm
(and update toolchain)
$ CROSS_COMPILE=arm-none-linux-gnueabihf- make ARCH=arm mrproper
$ CROSS_COMPILE=arm-none-linux-gnueabihf- make ARCH=arm vexpress_defconfig
$ grep -w CONFIG_MODULES .config
CONFIG_MODULES=y
$ grep "=m" .config
$ echo $?
1
$ CROSS_COMPILE=arm-none-linux-gnueabihf- make ARCH=arm Image -j5 > /dev/null
$ ls *.symvers
vmlinux.symvers
$ CROSS_COMPILE=arm-none-linux-gnueabihf- make ARCH=arm Image -j5 modules > /dev/null
$ ls *.symvers
Module.symvers vmlinux.symvers
So, `make modules` seems to become be mandatory. I'll go and update my scripts...
Cheers
Vladimir
>
>
>
>> Cheers
>> Vladimir
>
>
>
>
> --
> Best Regards
> Masahiro Yamada
>
next prev parent reply other threads:[~2021-03-05 14:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 16:21 Vladimir Murzin
2021-03-04 17:24 ` Masahiro Yamada
2021-03-05 14:15 ` Vladimir Murzin [this message]
2021-03-05 14:33 ` Masahiro Yamada
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=985bf10d-336c-61f6-8b9d-d8c6fb48634a@arm.com \
--to=vladimir.murzin@arm.com \
--cc=arnd@arndb.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
/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
all inboxes | Powered by JetHome®