linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Robin Murphy <robin.murphy@arm.com>
To: "Mohan Rao .vanimina" <mailtoc.mohanrao@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: linker script /arch/arm64/kernel/vmlinux.lds build error
Date: Wed, 7 Sep 2022 11:30:23 +0100	[thread overview]
Message-ID: <6f65d65b-0217-10d7-8e0c-d8ec6d95af44@arm.com> (raw)
In-Reply-To: <CAL_GTzigiNOMYkOPX1KDnagPhJtFNqSK=1USNbS0wUL4PW6-Uw@mail.gmail.com>

On 2022-09-06 19:13, Mohan Rao .vanimina wrote:
> Has anyone ever encountered the following issue.
> Actually I’m trying to configure the page size for 64KB for the AARCH
> 64 platform.
> 
> Build error:
> LTO vmlinux.o
> MODPOST vmlinux.symvers
> MODINFO modules.builtin.modinfo
> GEN modules.builtin
> LD  .tmp_vmlinux.kallsymsl
> ld.lld: error: k/arch/arm64/kernel/vmlinux.lds:72: symbol not found: PMD_SIZE
> 
> I started seeing this build issue after changing the default page size
> from ARM64_4K_PAGES to ARM64_64K_PAGES.
> 
> patch:
> choice
>              prompt “Page size”
> -          default ARM64_4K_PAGES
> +         default ARM64_64K_PAGES
>              help
>                   Page size ( translation granule) configuration.
> 

It sounds like you've most likely confused the build system into not 
rebuilding everything that should have been rebuilt. Hacking Kconfig 
sources is not the way to change your configuration; you should do that 
by editing .config, either manually or with tools like scripts/config or 
one of the interactive make targets.

However it looks like you're using LTO, so I guess there's also a chance 
that that could be at fault for failing to properly track some 
dependency that the config change affects. If you can still reproduce 
this behaviour by changing your config normally, it might be worth 
raising it with the Clang folks. FWIW I've never seen any issue 
reconfiguring the page size for GCC builds (without LTO).

Robin.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-09-07 10:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 18:13 linker script /arch/arm64/kernel/vmlinux.lds build error Mohan Rao .vanimina
2022-09-07 10:30 ` Robin Murphy [this message]
2022-09-15 15:40   ` Mohan Rao .vanimina
2022-09-20 12:20     ` Mark Rutland
2022-09-20 15:06       ` Sami Tolvanen

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=6f65d65b-0217-10d7-8e0c-d8ec6d95af44@arm.com \
    --to=robin.murphy@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mailtoc.mohanrao@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;
as well as URLs for NNTP newsgroup(s).