From: Borislav Petkov <bp@alien8.de>
To: Mirsad Todorovac <mtodorovac69@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Yuntao Wang <ytcoode@gmail.com>, Breno Leitao <leitao@debian.org>,
Brian Gerst <brgerst@gmail.com>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PROBLEM] ./arch/x86/include/asm/pgtable_32.h:59:5: error: "PTRS_PER_PMD" is not defined, evaluates to 0 [-Werror=undef]
Date: Mon, 8 Jul 2024 11:49:58 +0200 [thread overview]
Message-ID: <20240708094958.GAZou2Rq4bCMCVln1C@fat_crate.local> (raw)
In-Reply-To: <f79ee8f6-3fba-4c5f-9dc4-371906c529a8@gmail.com>
On Fri, Jul 05, 2024 at 11:52:30PM +0200, Mirsad Todorovac wrote:
> Hi, all!
>
> This is the result of testing randconfig with KCONFIG_SEED=0xEE7AB52F in next-20240703 vanilla tree on
> Ubuntu 22.04 LTS. GCC used is gcc (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0.
>
> The particular error is as follows:
>
> In file included from arch/x86/kernel/head_32.S:29:
> ./arch/x86/include/asm/pgtable_32.h:59:5: error: "PTRS_PER_PMD" is not defined, evaluates to 0 [-Werror=undef]
> 59 | #if PTRS_PER_PMD > 1
> | ^~~~~~~~~~~~
> cc1: all warnings being treated as errors
I can't reproduce that with your config ontop of
commit 0b58e108042b0ed28a71cd7edf5175999955b233 (HEAD, tag: refs/tags/next-20240703, refs/remotes/linux-next/master)
Author: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Wed Jul 3 16:14:20 2024 +1000
Add linux-next specific files for 20240703
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
$ make ARCH=i386 -j128 CC=gcc HOSTCC=gcc
...
OBJCOPY arch/x86/boot/setup.bin
BUILD arch/x86/boot/bzImage
Kernel: arch/x86/boot/bzImage is ready (#1)
Something's missing.
Did you do
$ git clean -dqfx
before building?
Note that that cmd will clear *everything* so you better check your local tree
before you run it:
$ git status
and then
$ git clean -dqfx
after having saved the files which you still need.
HTH.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-07-08 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 21:52 Mirsad Todorovac
2024-07-08 9:49 ` Borislav Petkov [this message]
2024-07-08 18:21 ` Mirsad Todorovac
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=20240708094958.GAZou2Rq4bCMCVln1C@fat_crate.local \
--to=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=mtodorovac69@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=ytcoode@gmail.com \
/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®