From: "chenjiahao (C)" <chenjiahao16@huawei.com> To: <masahiroy@kernel.org> Cc: <aou@eecs.berkeley.edu>, <ardb@kernel.org>, <arnd@arndb.de>, <catalin.marinas@arm.com>, <dennis@ausil.us>, <jszhang@kernel.org>, <linux-arch@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>, <nicolas@fjasle.eu>, <palmer@dabbelt.com>, <paul.walmsley@sifive.com>, <regressions@leemhuis.info>, <will@kernel.org> Subject: Re: [PATCH v2] arch: fix broken BuildID for arm64 and riscv Date: Fri, 12 May 2023 18:10:15 +0800 [thread overview] Message-ID: <f7a58629-05ae-18f4-d047-a2592f501b45@huawei.com> (raw) In-Reply-To: <20221226184537.744960-1-masahiroy@kernel.org> Hi, It seems this patch introduces a compile error on powerpc 85xx platform with CONFIG_RELOCATABLE enabled. To reproduce the problem, I compiled the mainline linux kernel with patch 99cb0d917ffa ("arch: fix broken BuildID for arm64 and riscv"), using configure file: arch/powerpc/configs/85xx-32bit.config and enabled CONFIG_RELOCATABLE manually. Then the compile log with Segmentation fault appeared as below: ... AR fs/proc/built-in.a AR fs/built-in.a AR built-in.a AR vmlinux.a LD vmlinux.o OBJCOPY modules.builtin.modinfo GEN modules.builtin MODPOST vmlinux.symvers UPD include/generated/utsversion.h CC init/version-timestamp.o LD .tmp_vmlinux.kallsyms1 Segmentation fault (core dumped) scripts/Makefile.vmlinux:34: recipe for target 'vmlinux' failed make[1]: *** [vmlinux] Error 139 Makefile:1252: recipe for target 'vmlinux' failed make: *** [vmlinux] Error 2 Could anyone reproduce above error, or have I missed anything else? Thanks, Jiahao _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: "chenjiahao (C)" <chenjiahao16@huawei.com> To: <masahiroy@kernel.org> Cc: <aou@eecs.berkeley.edu>, <ardb@kernel.org>, <arnd@arndb.de>, <catalin.marinas@arm.com>, <dennis@ausil.us>, <jszhang@kernel.org>, <linux-arch@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-kbuild@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>, <nicolas@fjasle.eu>, <palmer@dabbelt.com>, <paul.walmsley@sifive.com>, <regressions@leemhuis.info>, <will@kernel.org> Subject: Re: [PATCH v2] arch: fix broken BuildID for arm64 and riscv Date: Fri, 12 May 2023 18:10:15 +0800 [thread overview] Message-ID: <f7a58629-05ae-18f4-d047-a2592f501b45@huawei.com> (raw) In-Reply-To: <20221226184537.744960-1-masahiroy@kernel.org> Hi, It seems this patch introduces a compile error on powerpc 85xx platform with CONFIG_RELOCATABLE enabled. To reproduce the problem, I compiled the mainline linux kernel with patch 99cb0d917ffa ("arch: fix broken BuildID for arm64 and riscv"), using configure file: arch/powerpc/configs/85xx-32bit.config and enabled CONFIG_RELOCATABLE manually. Then the compile log with Segmentation fault appeared as below: ... AR fs/proc/built-in.a AR fs/built-in.a AR built-in.a AR vmlinux.a LD vmlinux.o OBJCOPY modules.builtin.modinfo GEN modules.builtin MODPOST vmlinux.symvers UPD include/generated/utsversion.h CC init/version-timestamp.o LD .tmp_vmlinux.kallsyms1 Segmentation fault (core dumped) scripts/Makefile.vmlinux:34: recipe for target 'vmlinux' failed make[1]: *** [vmlinux] Error 139 Makefile:1252: recipe for target 'vmlinux' failed make: *** [vmlinux] Error 2 Could anyone reproduce above error, or have I missed anything else? Thanks, Jiahao
next prev parent reply other threads:[~2023-05-12 10:10 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-26 18:45 [PATCH v2] arch: fix broken BuildID for arm64 and riscv Masahiro Yamada 2022-12-26 18:45 ` Masahiro Yamada 2022-12-26 18:45 ` Masahiro Yamada 2022-12-29 16:22 ` Palmer Dabbelt 2022-12-29 16:22 ` Palmer Dabbelt 2022-12-29 16:22 ` Palmer Dabbelt 2023-01-02 4:16 ` Nathan Chancellor 2023-01-02 4:16 ` Nathan Chancellor 2023-01-02 4:16 ` Nathan Chancellor 2023-01-02 7:08 ` Linux kernel regression tracking (#info) 2023-01-02 7:08 ` Linux kernel regression tracking (#info) 2023-01-02 7:08 ` Linux kernel regression tracking (#info) 2023-01-05 3:22 ` Masahiro Yamada 2023-01-05 3:22 ` Masahiro Yamada 2023-01-05 3:22 ` Masahiro Yamada 2023-01-05 9:21 ` Andreas Schwab 2023-01-05 9:21 ` Andreas Schwab 2023-01-05 9:21 ` Andreas Schwab 2023-01-05 9:27 ` Ard Biesheuvel 2023-01-05 9:27 ` Ard Biesheuvel 2023-01-05 9:27 ` Ard Biesheuvel 2023-01-05 11:14 ` Michael Ellerman 2023-01-05 11:14 ` Michael Ellerman 2023-01-05 11:14 ` Michael Ellerman 2023-01-05 13:49 ` Masahiro Yamada 2023-01-05 13:49 ` Masahiro Yamada 2023-01-05 13:49 ` Masahiro Yamada 2023-05-12 10:10 ` chenjiahao (C) [this message] 2023-05-12 10:10 ` chenjiahao (C)
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=f7a58629-05ae-18f4-d047-a2592f501b45@huawei.com \ --to=chenjiahao16@huawei.com \ --cc=aou@eecs.berkeley.edu \ --cc=ardb@kernel.org \ --cc=arnd@arndb.de \ --cc=catalin.marinas@arm.com \ --cc=dennis@ausil.us \ --cc=jszhang@kernel.org \ --cc=linux-arch@vger.kernel.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kbuild@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=masahiroy@kernel.org \ --cc=nicolas@fjasle.eu \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=regressions@leemhuis.info \ --cc=will@kernel.org \ /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: linkBe 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.