[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1907201133000.1782@nanos.tec.linutronix.de>
Date: Sat, 20 Jul 2019 11:34:27 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Mike Lothian <mike@...eburn.co.uk>
cc: Masahiro Yamada <yamada.masahiro@...ionext.com>,
Nathan Chancellor <natechancellor@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
X86 ML <x86@...nel.org>, "H.J. Lu" <hjl.tools@...il.com>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
"Theodore Y. Ts'o" <tytso@....edu>, linux-arch@...r.kernel.org
Subject: Re: [PATCH v2] kbuild: Fail if gold linker is detected
On Sat, 20 Jul 2019, Mike Lothian wrote:
> On Wed, 17 Jul 2019 at 08:57, Thomas Gleixner <tglx@...utronix.de> wrote:
> I've done a bit more digging, I had a second machine that was building
> Linus's tree just fine with ld.gold
>
> I tried forcing ld.bfd on the problem machine and got this:
>
> ld.bfd: arch/x86/boot/compressed/head_64.o: warning: relocation in
> read-only section `.head.text'
> ld.bfd: warning: creating a DT_TEXTREL in object
>
> I had a look at the differences in the kernel configs and noticed this:
>
> CONFIG_RANDOMIZE_BASE=y
> CONFIG_X86_NEED_RELOCS=y
> CONFIG_PHYSICAL_ALIGN=0x1000000
> CONFIG_DYNAMIC_MEMORY_LAYOUT=y
> CONFIG_RANDOMIZE_MEMORY=y
> CONFIG_RANDOMIZE_MEMORY_PHYSICAL_PADDING=0x0
>
> Unsetting CONFIG_RANDOMIZE_BASE=y gets things working for me with ld.gold again
Can you please provide the full config? I have the above set here and it
builds just fine.
> In light of this - can we drop this patch?
No. I'm not going to deal with unsupported tools.
Thanks,
tglx
Powered by blists - more mailing lists