From: Marco Bonelli <marco@mebeim.net>
To: Alexandre Ghiti <alex@ghiti.fr>,
"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: Wed, 4 Jun 2025 15:52:05 +0200 (CEST) [thread overview]
Message-ID: <1338988468.1011577.1749045125350@privateemail.com> (raw)
In-Reply-To: <c239ee1b-f201-4e7b-80f8-03a7fb02b666@ghiti.fr>
> Can you attach your full config?
Here it is: https://pastebin.com/raw/wL2Q38g0 - uploaded to pastebin to
avoid clogging everyone's inbox.
> I unfortunately cannot reproduce this issue locally, I tried on both
> v6.15 and latest linus master, with gcc 13.1.0 and gcc 14.2.0 . I made
> sure that I have FTRACE, ZSTD_COMPRESS and DEBUG_INFO enabled.
Are you building on a x86-64 host? Maybe something in my build environment
is relevant (not sure what it could be). I am building on x86-64 Debian 12
with host GCC 12.2.0, target cross GCC 14.2.0 [1].
Here is a minimal Dockerfile that reproduces the issue (docker build should
fail on the last command when it gets to MODPOST vmlinux.symvers):
# docker build --progress=plain .
FROM debian:12
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && \
apt-get install -y \
build-essential git make gcc-12 binutils util-linux bc gawk flex \
bison dwarves tar wget
WORKDIR /work
RUN git clone --depth 1 --single-branch --branch v6.15 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
RUN wget 'https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/14.2.0/x86_64-gcc-14.2.0-nolibc-riscv32-linux.tar.xz'
RUN tar xf x86_64-gcc-14.2.0-nolibc-riscv32-linux.tar.xz
WORKDIR /work/linux
ENV PATH=/work/gcc-14.2.0-nolibc/riscv32-linux/bin:$PATH
ENV CROSS_COMPILE=riscv32-linux-
ENV ARCH=riscv
RUN 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
RUN make -j19 vmlinux
Hope this helps. Let me know if you need any additional info or test.
[1]: https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/14.2.0/x86_64-gcc-14.2.0-nolibc-riscv32-linux.tar.xz
--
Marco Bonelli
next prev parent reply other threads:[~2025-06-04 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 21:40 Broken 32-bit riscv debug build with ZSTD and FTRACE Marco Bonelli
2025-05-31 11:52 ` Marco Bonelli
2025-06-04 12:44 ` Alexandre Ghiti
2025-06-04 13:52 ` Marco Bonelli [this message]
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=1338988468.1011577.1749045125350@privateemail.com \
--to=marco@mebeim.net \
--cc=alex@ghiti.fr \
--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