public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nick Terrell <terrelln@fb.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: v5.17-rc3 compile failure on aarch64
Date: Thu, 17 Feb 2022 19:59:10 +0800	[thread overview]
Message-ID: <797f79cb-3b9b-e8b1-b2c3-5f9aba270ae7@gmx.com> (raw)
In-Reply-To: <Yg42iEZwHS//aFAj@lakrids>

[-- Attachment #1: Type: text/plain, Size: 2700 bytes --]



On 2022/2/17 19:50, Mark Rutland wrote:
> On Thu, Feb 17, 2022 at 04:37:49PM +0800, Qu Wenruo wrote:
>> Hi,
>
> Hi,
>
> [adding LAKML so other arm/arm64 folk can chime in]
>
>> Recently I found v5.17-rc3 kernel failed to compile on my aarch64 setup,
>> it failed with the following error messages:
>>
>>    AR      lib/zstd/built-in.a
>>    LD [M]  lib/zstd/zstd_compress.o
>> ld: __patchable_function_entries has both ordered
>> [`__patchable_function_entries' in lib/zstd/common/entropy_common.o] and
>> unordered [`__patchable_function_entries' in
>> lib/zstd/common/error_private.o] sections
>> ld: final link failed: bad value
>> make[2]: *** [scripts/Makefile.build:484: lib/zstd/zstd_compress.o] Error 1
>> make[1]: *** [scripts/Makefile.build:550: lib/zstd] Error 2
>> make: *** [Makefile:1831: lib] Error 2
>> make: *** Waiting for unfinished jobs....
>
> Uh-oh; that doesn't look good.
>
> In case this is configuration-dependent, could you share your .config?

Sure, attached.

>
>> But the same code base compiles fine inside my x86_64 VM.
>>
>> The aarch64 environment is an VM running on RockPro64 or RPI CM4.
>>
>> With a little older gcc (v10.2.0) and bintuils (2.35).
>
> Is this a custom-built toolchain, or one shipped by a distribution?

Shipped by distro (ArchlinuxARM), native, no cross chain.

And it's mostly upstream, or very lightly backported.

>
> If possible, can you see if you can reproduce this with one of the
> kernel.org cross toolchains:
>
>    https://mirrors.edge.kernel.org/pub/tools/crosstool/
>
> ... because if you can, that will be much easier for someone else to
> reproduce and analyse.
>
> The closest builds are 9.3.0 and 10.3.0, for both arm64 and x86_64.

Sorry, not cross tool chain but native toolchain.

>
> FWIW, I had a go building v5.17-rc3 defconfig with ftrace and zstd bits
> eanbled with both GCC 9.3.0 and GCC 10.3.0, and I could not reproduce
> the problem.

After the incident, I tried the following things, and got it solved:

- Upgrade to gcc 11.1.0 and binutils 2.36.1
   The same kernel base, no "make clean"

   And got the same error.

- "make clean" for the kernel and recompile
   Now the failure is gone.

   Thus I guess it's mostly some old .o is being re-used...

Sorry for the inconvenience, I should just re-compile (even it's super
time-consuming) before reporting...

Thanks,
Qu

>
> Thanks,
> Mark.
>
>> While for my x86_64 VM it has newer gcc (11.1.0) and binutiles (2.36.1)
>>
>> I'm super happy to upgrade my tool chain for my aarch64 VM, but I'm a
>> little concerned if there is something worthy fixed.
>>
>> Thanks,
>> Qu

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 38334 bytes --]

[-- Attachment #3: Type: text/plain, Size: 176 bytes --]

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

  reply	other threads:[~2022-02-17 12:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <85bfe02c-9432-c5b0-04e0-8096adf37b93@gmx.com>
2022-02-17 11:50 ` v5.17-rc3 compile failure on aarch64 Mark Rutland
2022-02-17 11:59   ` Qu Wenruo [this message]
2022-02-17 13:41     ` Mark Rutland

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=797f79cb-3b9b-e8b1-b2c3-5f9aba270ae7@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=terrelln@fb.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