BLD: many warnings around _LIBCPP_ENABLE_ASSERT on macos

Meson is setting -D_LIBCPP_ENABLE_ASSERT on macos, but that has been deprecated and its use emits a warning when compiling. Upstream meson fixed the warning in mesonbuild/meson#14548. Are we due for a round of updating the vendored meson code soon or should we merge that change without updating the rest?

I'm fine with backporting that change separately, because I don't have much time to work through a larger update this week. I can always make time if it's urgent of course, but this doesn't feel all that urgent right now.

Is there a rough guide to the vendored meson update process? Maybe others could help so the burden is not all on you

It's about resolving potentially tricky merge conflicts, so the first approach may not work. But ideally the process is to:

Merge a new upstream release tag or recent commit on master into the main-numpymeson branch of our fork,
Test that that works with all CI on this repo, by opening a PR or testing on your own fork
Then review the diff on the merge (e.g., see Update to v1.6.1 meson#18 (review) for last time) and merge the PR on numpy/meson.
Then bump the submodule version in this repo.

Closing, an update of meson is preferable to a single PR backport.

Navigation Menu

Repository navigation

BLD: many warnings around _LIBCPP_ENABLE_ASSERT on macos #29454

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

BLD: many warnings around _LIBCPP_ENABLE_ASSERT on macos #29454

Description

Activity

rgommers commented on Jul 29, 2025

mattip commented on Jul 29, 2025

rgommers commented on Jul 30, 2025

mattip commented on Aug 1, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions