From: Jeff King <peff@peff.net>
To: Patrick Steinhardt <ps@pks.im>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: win+Meson test failures due to ps/build-meson-fixes-0130 topic?
Date: Wed, 26 Feb 2025 03:20:02 -0500 [thread overview]
Message-ID: <20250226082002.GA30633@coredump.intra.peff.net> (raw)
In-Reply-To: <20250226074653.GA27455@coredump.intra.peff.net>
On Wed, Feb 26, 2025 at 02:46:53AM -0500, Jeff King wrote:
> I'd imagine that if I did a complete "rm -rf build && meson setup build"
> it would work. But it's pretty lousy to have to do that preemptively
> during a bisection.
Looks like this runs even deeper. On my Linux machine:
$ git checkout origin/next
$ meson setup build
[...ok...]
$ meson compile -C build
[...ok...]
$ git checkout origin/master
$ meson compile -C build
[...]
../meson.build:215:35: ERROR: The `!=` operator of array does not accept objects of type str ()
FAILED: build.ninja
/usr/bin/meson --internal regenerate /home/peff/compile/git .
ninja: error: rebuilding 'build.ninja': subcommand failed
$ rm -rf build
$ meson setup build
$ meson compile -C build
[...ok again...]
I'm hoping you can tell me I'm holding it wrong, and there's some way to
do an incremental build when crossing these sorts of boundaries (without
blowing away all of the build products).
I do at least use ccache which makes the "rm -rf" case a little less
painful.
-Peff
next prev parent reply other threads:[~2025-02-26 8:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-25 19:45 win+Meson test failures due to ps/build-meson-fixes-0130 topic? Junio C Hamano
2025-02-26 5:45 ` Patrick Steinhardt
2025-02-26 7:27 ` Jeff King
2025-02-26 7:35 ` Patrick Steinhardt
2025-02-26 7:46 ` Jeff King
2025-02-26 8:20 ` Jeff King [this message]
2025-02-26 9:15 ` Patrick Steinhardt
2025-02-26 22:07 ` Jeff King
2025-02-26 15:55 ` Junio C Hamano
2025-02-26 16:29 ` Patrick Steinhardt
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=20250226082002.GA30633@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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