From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: linux5.9-5.9.1.
Date: Sun, 18 Oct 2020 18:44:40 +0200 [thread overview]
Message-ID: <20201018164440.EOPUOm5npKt_G5uZlJbu2tVAYXPpwOFo4sxhTGwtA-A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25702@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/25702#issuecomment-711283867
Comment:
I tried removing the `-mgeneral-regs-only` flag and hit another error before linking `vmlinux` when `pahole` is run:
```cc
GEN modules.builtin
LD .tmp_vmlinux.btf
BTF .btf.vmlinux.bin.o
PAHOLE: Error: Found symbol of zero size when encoding btf (sym: '__kvm_nvhe_arm64_ssbd_callback_required', cu: 'arch/arm64/kernel/cpu_errata.c').
PAHOLE: Error: Use '-j' or '--force' to ignore such symbols and force emit the btf.
scripts/link-vmlinux.sh: line 141: 43837 Segmentation fault LLVM_OBJCOPY=${OBJCOPY} ${PAHOLE} -J ${1}
LD .tmp_vmlinux.kallsyms1
KSYM .tmp_vmlinux.kallsyms1.o
LD .tmp_vmlinux.kallsyms2
KSYM .tmp_vmlinux.kallsyms2.o
LD vmlinux
BTFIDS vmlinux
FAILED: load BTF from vmlinux: Unknown error -2make: *** [Makefile:1162: vmlinux] Error 255
=> ERROR: linux5.9-5.9.1_1: do_build: 'make ARCH=$arch ${_version} ${_cross} ${makejobs} ${_args}' exited with 2
=> ERROR: in do_build() at srcpkgs/linux5.9/template:110
```
Perhaps `${PAHOLE} -J` should be `${PAHOLE} -j`. The manual page `pahole(1)` lists neither of these flags...
next prev parent reply other threads:[~2020-10-18 16:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 4:49 [PR PATCH] " ericonr
2020-10-18 4:50 ` [PR PATCH] [Updated] " ericonr
2020-10-18 10:06 ` q66
2020-10-18 13:37 ` pullmoll
2020-10-18 13:41 ` pullmoll
2020-10-18 13:56 ` pullmoll
2020-10-18 14:03 ` pullmoll
2020-10-18 15:10 ` pullmoll
2020-10-18 16:29 ` ericonr
2020-10-18 16:41 ` [PR PATCH] [Updated] " ericonr
2020-10-18 16:44 ` pullmoll [this message]
2020-10-18 16:56 ` pullmoll
2020-10-18 17:03 ` pullmoll
2020-10-18 17:39 ` jnbr
2020-10-18 18:28 ` q66
2020-10-18 18:28 ` q66
2020-10-18 18:29 ` pullmoll
2020-10-18 18:31 ` pullmoll
2020-10-18 18:53 ` jnbr
2020-10-18 19:47 ` q66
2020-10-18 21:07 ` [PR PATCH] [Updated] " ericonr
2020-10-18 21:09 ` ericonr
2020-10-18 21:57 ` ericonr
2020-10-18 22:11 ` ericonr
2020-10-18 23:02 ` [PR PATCH] [Updated] " ericonr
2020-10-18 23:04 ` ericonr
2020-10-18 23:29 ` [PR PATCH] [Updated] " ericonr
2020-10-19 19:32 ` ericonr
2020-10-19 21:57 ` ericonr
2020-10-20 19:01 ` ericonr
2020-10-20 19:10 ` [PR PATCH] [Updated] " ericonr
2020-10-22 1:41 ` ericonr
2020-10-29 22:50 ` [PR PATCH] [Updated] " ericonr
2020-11-01 20:44 ` ericonr
2020-11-02 11:53 ` sgn
2020-11-02 19:18 ` arthur-morosov
2020-11-02 19:19 ` arthur-morosov
2020-11-04 15:03 ` [PR PATCH] [Merged]: " ericonr
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=20201018164440.EOPUOm5npKt_G5uZlJbu2tVAYXPpwOFo4sxhTGwtA-A@z \
--to=pullmoll@users.noreply.github.com \
--cc=ml@inbox.vuxu.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: 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;
as well as URLs for NNTP newsgroup(s).