From: David Gibson <david@gibson.dropbear.id.au>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>
Cc: Jan Palus <jpalus@fastmail.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/3] Fix broken build with -DNDEBUG
Date: Fri, 15 May 2026 14:13:09 +1000 [thread overview]
Message-ID: <20260515041312.317644-1-david@gibson.dropbear.id.au> (raw)
Fix the trivial but nasty with -DNDEBUG builds recently reported by
Jan Palus. While we're there, add a couple of extra build tests.
These wouldn't actually catch this problem, but they're better than
nothing and do catch the #include problem I also spotted.
David Gibson (3):
test: Extend exeter build tests to cover more recent binaries
Fix build with -DNDEBUG
test: Add test for builds with -DNDEBUG
test/build/build.py | 25 +++++++++++++++++++++----
util.h | 3 ++-
2 files changed, 23 insertions(+), 5 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-15 8:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 4:13 David Gibson [this message]
2026-05-15 4:13 ` [PATCH 1/3] test: Extend exeter build tests to cover more recent binaries David Gibson
2026-05-15 4:13 ` [PATCH 2/3] Fix build with -DNDEBUG David Gibson
2026-05-15 11:05 ` Jan Palus
2026-05-16 6:28 ` David Gibson
2026-05-16 9:27 ` Stefano Brivio
2026-05-16 11:12 ` David Gibson
2026-05-15 4:13 ` [PATCH 3/3] test: Add test for builds " David Gibson
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=20260515041312.317644-1-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=jpalus@fastmail.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@redhat.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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).