All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nick Terrell <terrelln@fb.com>
Subject: v5.17-rc3 compile failure on aarch64
Date: Thu, 17 Feb 2022 16:37:49 +0800	[thread overview]
Message-ID: <85bfe02c-9432-c5b0-04e0-8096adf37b93@gmx.com> (raw)

Hi,

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....

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).

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

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-17  8:37 Qu Wenruo [this message]
2022-02-17 11:50 ` v5.17-rc3 compile failure on aarch64 Mark Rutland
2022-02-17 11:50   ` Mark Rutland
2022-02-17 11:59   ` Qu Wenruo
2022-02-17 11:59     ` Qu Wenruo
2022-02-17 13:41     ` Mark Rutland
2022-02-17 13:41       ` Mark Rutland
2022-02-18 23:10 ` Nick Terrell

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=85bfe02c-9432-c5b0-04e0-8096adf37b93@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.