[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9f32e509-95b1-6a5a-aba2-664af4af37a8@infradead.org>
Date: Mon, 22 May 2023 19:28:45 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Alexandre Ghiti <alex@...ti.fr>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Conor Dooley <conor@...nel.org>
Subject: Re: linux-next: Tree for May 15 (several RV64 build errors)
Hi,
On 5/19/23 03:42, Alexandre Ghiti wrote:
>>> /opt/crosstool/gcc-12.2.0-nolibc/riscv64-linux/bin/riscv64-linux-ld: section .data LMA [000000000041a000,00000000075bffd7] overlaps section .text LMA [00000000000f09d4,00000000033562ab]
>>> /opt/crosstool/gcc-12.2.0-nolibc/riscv64-linux/bin/riscv64-linux-ld: section .init.pi.text LMA [00000000033562ac,0000000003359137] overlaps section .data LMA [000000000041a000,00000000075bffd7]
>>
>>
>> I'll check this one too which seems to be related to kernel/pi introduction.
>
>
> Thanks to Bjorn: this is caused by XIP_KERNEL, which is known to have limited size, hence the overlap, so no fix for this one. Is there a way to exclude this config from randconfig?
Does this mean exclude XIP_KERNEL or something else from randconfigs?
thanks.
--
~Randy
Powered by blists - more mailing lists