From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-kernel] d/rules: don't strip debug kernel image
Date: Wed, 08 Oct 2025 14:08:36 +0200 [thread overview]
Message-ID: <1759925312.5beu9qj8n9.astroid@yuna.none> (raw)
In-Reply-To: <20250904121325.778823-1-f.gruenbichler@proxmox.com>
ping
On September 4, 2025 2:11 pm, Fabian Grünbichler wrote:
> the regular one is already compressed and stripped, but the debug one enabled
> via the custom profile would be stripped because it is detected as static
> executable by dh_strip.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
> found this in a local branch, was prompted by a forum thread:
> https://forum.proxmox.com/threads/help-compiling-an-unstripped-pve-vmlinux-file.168299/
>
> debian/rules | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/debian/rules b/debian/rules
> index 7f6cadf..628480e 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -144,7 +144,7 @@ install: .install_mark .tools_install_mark .headers_install_mark .usr_headers_in
>
> binary: install
> debian/rules fwcheck abicheck
> - dh_strip -N$(PMX_HEADER_PKG) -N$(PMX_USR_HEADER_PKG)
> + dh_strip -N$(PMX_HEADER_PKG) -N$(PMX_USR_HEADER_PKG) -Xvmlinux -Xvmlinuz
> dh_makeshlibs
> dh_shlibdeps
> dh_installdeb
> --
> 2.47.3
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-10-08 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 12:11 Fabian Grünbichler
2025-10-08 12:08 ` Fabian Grünbichler [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=1759925312.5beu9qj8n9.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.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