From: Marco Bonelli <marco@mebeim.net>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "terrelln@fb.com" <terrelln@fb.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"mhiramat@kernel.org" <mhiramat@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>
Subject: Re: Broken 32-bit riscv debug build with ZSTD and FTRACE
Date: Sat, 31 May 2025 13:52:51 +0200 (CEST) [thread overview]
Message-ID: <1552795452.650306.1748692371190@privateemail.com> (raw)
In-Reply-To: <960240908.630790.1748641210849@privateemail.com>
> Steps to reproduce:
>
> export ARCH=riscv CROSS_COMPILE=riscv32-linux-
> make distclean
> make defconfig
> make 32-bit.config
> ./scripts/config \
> -e DEBUG_KERNEL \
> -e DEBUG_INFO \
> -e DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT \
> -d DEBUG_INFO_NONE \
> -d DEBUG_INFO_REDUCED
> make olddefconfig
> make -j vmlinux
Sorry, forgot to add "-e FTRACE" to the steps above. Here it is:
export ARCH=riscv CROSS_COMPILE=riscv32-linux-
make distclean
make defconfig
make 32-bit.config
./scripts/config \
-e DEBUG_KERNEL \
-e DEBUG_INFO \
-e DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT \
-d DEBUG_INFO_NONE \
-d DEBUG_INFO_REDUCED \
-e FTRACE
make olddefconfig
make -j vmlinux
Everything else still applies.
--
Marco Bonelli
next prev parent reply other threads:[~2025-05-31 12:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 21:40 Marco Bonelli
2025-05-31 11:52 ` Marco Bonelli [this message]
2025-06-04 12:44 ` Alexandre Ghiti
2025-06-04 13:52 ` Marco Bonelli
2025-06-06 19:42 ` Marco Bonelli
2025-06-12 12:46 ` Alexandre Ghiti
2025-06-17 1:48 ` Marco Bonelli
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=1552795452.650306.1748692371190@privateemail.com \
--to=marco@mebeim.net \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®