From: Nathan Chancellor <nathan@kernel.org>
To: Nicolas Schier <nsc@kernel.org>, Nathan Chancellor <nathan@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Lukas Herbolt <lukas@herbolt.com>
Subject: Re: [PATCH] kbuild: rpm-pkg: Fix manual debuginfo generation when using .src.rpm
Date: Wed, 18 Feb 2026 13:49:06 -0700 [thread overview]
Message-ID: <177144774696.1769768.10484893215467443887.b4-ty@kernel.org> (raw)
In-Reply-To: <20260213-fix-debuginfo-srcrpm-pkg-v1-1-45cd0c0501b9@kernel.org>
On Fri, 13 Feb 2026 01:45:13 -0500, Nathan Chancellor wrote:
> Commit 62089b804895 ("kbuild: rpm-pkg: Generate debuginfo package
> manually") added uses of OBJCOPY and READELF, variables from Kbuild.
> These variables are defined and work properly when using the binrpm-pkg
> target because rpmbuild is run within Kbuild. However, these variables
> are not defined when building from a source RPM package generated with
> the srcrpm-pkg target, breaking the build when generating the debug info
> subpackage.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/kbuild/linux.git kbuild-fixes
Thanks!
[1/1] kbuild: rpm-pkg: Fix manual debuginfo generation when using .src.rpm
https://git.kernel.org/kbuild/c/afdfb71c018e9
Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped or
reverted. Patches applied to an "unstable" branch are accepted pending
wider testing in -next and any post-commit review; they will generally
be moved to the main branch in a week if no issues are found.
Best regards,
--
Nathan Chancellor <nathan@kernel.org>
prev parent reply other threads:[~2026-02-18 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 6:45 Nathan Chancellor
2026-02-18 20:49 ` Nathan Chancellor [this message]
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=177144774696.1769768.10484893215467443887.b4-ty@kernel.org \
--to=nathan@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@herbolt.com \
--cc=nsc@kernel.org \
--cc=stable@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
all inboxes | Powered by JetHome®