From: "Daniel P. Berrangé" <berrange@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, "Zhao Liu" <zhao1.liu@intel.com>,
"Laurent Vivier" <lvivier@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH 3/3] build: Add "-d keeprsp" to Ninja flags
Date: Mon, 9 Nov 2026 19:27:54 +0000 [thread overview]
Message-ID: <avIeunGVydLiZ9O8@redhat.com> (raw)
In-Reply-To: <20261109183605.3210043-4-jsnow@redhat.com>
On Mon, Nov 09, 2026 at 01:36:05PM -0500, John Snow wrote:
> When auditing compilation, it is helpful to be able to see all of the
> object files passed during the linking step, which ninja can obscure
> behind temporary .rsp "response files". Normally, these are deleted
> immediately afterwards - but for debugging purposes, it is helpful to
> leave them behind to understand what went wrong.
>
> Signed-off-by: John Snow <jsnow@redhat.com>
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> diff --git a/Makefile b/Makefile
> index 54547a37b1a..9dda1b3c89a 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -151,7 +151,7 @@ NINJAFLAGS = \
> $(filter-out -j, \
> $(or $(filter -l% -j%, $(MAKEFLAGS)), \
> $(if $(filter --jobserver-auth=%, $(MAKEFLAGS)),, -j1))) \
> - -d keepdepfile
> + -d keepdepfile $(if $(DEBUG),-d keeprsp)
> ninja-cmd-goals += $(or $(MAKECMDGOALS), all)
> ninja-cmd-goals += $(foreach g, $(MAKECMDGOALS), $(.ninja-goals.$g))
Alternatively we hardcode our makefile to raise meson's
annoyingly pessimistic defaults
export MESON_RSP_THRESHOLD=126976
provided we detect we're not running a build inside Wine, or just
blindly assume no one is quite that crazy :-)
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-11-09 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 18:36 [PATCH 0/3] build: small build system changes John Snow
2026-11-09 18:36 ` [PATCH 1/3] build: remove vestigial CONFIG_SGA John Snow
2026-11-09 19:24 ` Daniel P. Berrangé
2026-11-09 18:36 ` [PATCH 2/3] build: update CONFIG_PVPANIC John Snow
2026-11-09 19:25 ` Daniel P. Berrangé
2026-11-09 18:36 ` [PATCH 3/3] build: Add "-d keeprsp" to Ninja flags John Snow
2026-11-09 19:27 ` Daniel P. Berrangé [this message]
2026-11-10 14:59 ` John Snow
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=avIeunGVydLiZ9O8@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=farosas@suse.de \
--cc=jsnow@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhao1.liu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.