From: Alexander Coffin <alex@cyberialabs.net>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Subject: KCFLAGS vs KCPPFLAGS for -fdebug-prefix-map
Date: Sat, 28 Feb 2026 20:34:37 -0800 [thread overview]
Message-ID: <b8dfe7035d19fd611b9be55ee3145fdb@purelymail.com> (raw)
Hello,
From personally building the kernel a few months ago (reproducibly) one
of the parts that was incorrect in the docs was that is says to use
KCFLAGS when you should use KCPPFLAGS for the following. I had forgotten
to report this until now and I'm not sure exactly what is expected to
make a patch to the Kernel docs, so I am hoping someone else can do the
probably one line fix (or maybe 2 if you count the other reference to
KCFLAGS in the file).
> When the kernel is built out-of-tree, debug information may include
> absolute filenames for the source files. This must be overridden by
> including the ``-fdebug-prefix-map`` option in the `KCFLAGS`_ variable.
from `Documentation/kbuild/reproducible-builds.rst`.
Regards,
Alex Coffin
next reply other threads:[~2026-03-01 4:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-01 4:34 Alexander Coffin [this message]
2026-03-02 22:29 ` KCFLAGS vs KCPPFLAGS for -fdebug-prefix-map Nathan Chancellor
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=b8dfe7035d19fd611b9be55ee3145fdb@purelymail.com \
--to=alex@cyberialabs.net \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.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: 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