From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Mauro Rossi <issor.oruam@gmail.com>
Cc: netdev@vger.kernel.org, kabel@kernel.org,
Chih-Wei Huang <cwhuang@android-x86.org>
Subject: Re: FYI: net/phy/marvell10g: android kernel builing error due to modpost error
Date: Mon, 18 Apr 2022 11:08:54 +0100 [thread overview]
Message-ID: <Yl04ttYN95VCXan4@shell.armlinux.org.uk> (raw)
In-Reply-To: <CAEQFVGYURjcCA741koGF5aeRoymwh-h+_evP5cqAxE4U8UVnbA@mail.gmail.com>
On Mon, Apr 18, 2022 at 11:22:12AM +0200, Mauro Rossi wrote:
> At the final stage of building Linux 5.18-rc3 with the necessary AOSP
> changes, I am getting the following building error:
>
> MODPOST modules-only.symvers
> ERROR: modpost: "__compiletime_assert_344"
> [drivers/net/phy/marvell10g.ko] undefined!
> make[2]: *** [/home/utente/r-x86_kernel/kernel/scripts/Makefile.modpost:134:
> modules-only.symvers] Error 1
> make[2]: *** Deleting file 'modules-only.symvers'
> make[1]: *** [/home/utente/r-x86_kernel/kernel/Makefile:1749: modules] Error 2
> make[1]: *** Waiting for unfinished jobs....
>
> It never happened before throughout all my previous android-x86 kernel
> rc cycle build tests, which spanned from linux version 5.10 to linux
> version 5.18rc
As far as I'm aware, with mainline kernels, marvell10g builds fine.
I'm not sure how to work back from "__compiletime_assert_344" to
where the problem could be. The "344" appears to be generated by
the __COUNTER__ macro - and I don't know how that macro works (debian
annoyingly don't package the GCC info docs, and the info files I have
are out of date.)
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2022-04-18 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 9:22 FYI: net/phy/marvell10g: android kernel builing error due to modpost error Mauro Rossi
2022-04-18 10:08 ` Russell King (Oracle) [this message]
2022-04-19 16:39 ` Mauro Rossi
2022-05-01 18:51 ` Mauro Rossi
2022-05-01 21:28 ` Andrew Lunn
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=Yl04ttYN95VCXan4@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=cwhuang@android-x86.org \
--cc=issor.oruam@gmail.com \
--cc=kabel@kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.