Skip to content

meson detection broken (on Windows?) in latest release #108

Closed

Activity

  1. lucascolley commented on Apr 2, 2026

    @lucascolley
    Author
  2. rgommers commented on Apr 2, 2026

    @rgommers
    Member

    I already just noticed, working on a fix. Due to #106 (comment).

  3. virtuald commented on Apr 2, 2026

    @virtuald
    Collaborator

    I made a fix for hatch-meson at virtuald/hatch-meson#14 -- a fix for meson-python would likely be very similar.

  4. rgommers commented on Apr 2, 2026

    @rgommers
    Member

    Thanks for sharing @virtuald, that's a useful PR.

  5. rgommers commented on Apr 2, 2026

    @rgommers
    Member

    @lucascolley my take is that:

    1. For spin we'll want to do a similar thing as for hatch-meson, because that is the use case where we're already in the build environment. So it can continue to work without setting any environment variable.
    2. For building with build isolation, this improves things. We already use export PKG_CONFIG_PATH there to point at a scipy_openblas in the root (rather than the isolated) environment.
  6. lucascolley commented on Apr 2, 2026

    @lucascolley
    Author

    sounds fine

  7. lucascolley commented on Jun 6, 2026

    @lucascolley
    Author

    any news here?

  8. mhsmith commented on Aug 8, 2026

    @mhsmith

    I think the actual reason meson fails to detect pkgconf might be that pkgconf --version gives no output when PKG_CONFIG_PATH is set:

    (pkgconf) msmith@MacBook-Pro ~ % pip list
    Package Version
    ------- -----------
    pip     26.1.2
    pkgconf 3.0.1.post0
    (pkgconf) msmith@MacBook-Pro ~ % echo $PKG_CONFIG_PATH
    
    (pkgconf) msmith@MacBook-Pro ~ % pkgconf --version                         
    /Users/msmith/.venv/pkgconf/bin/pkgconf:6: UserWarning: PKG_CONFIG_PATH not specified, and the system is unavailable! The 'pkgconf' executable provided by pkgconf-pypi does not support searching for system-level .pc files, you must provide a search path instead. If you want the search path to be computed from the installed Python packages, please use the 'pkgconf-pypi' executable instead, or set FORCE_PKGCONF_PYPI.
      sys.exit(_vanilla_entrypoint())
    3.0.1
    (pkgconf) msmith@MacBook-Pro ~ % PKG_CONFIG_PATH=whatever pkgconf --version     
    (pkgconf) msmith@MacBook-Pro ~ % pkgconf-pypi --version                         
    3.0.1
    (pkgconf) msmith@MacBook-Pro ~ % PKG_CONFIG_PATH=whatever pkgconf-pypi --version
    3.0.1
  9. mhsmith commented on Oct 17, 2026

    @mhsmith

    The behavior in my previous comment has been fixed in pkgconf 3.0.7.post0. Should this issue be closed now?

  10. lucascolley commented on Oct 17, 2026

    @lucascolley
    Author

    11. The behavior in my previous comment has been fixed in pkgconf 3.0.7.post0. Should this issue be closed now?

    Let me see how CI looks on scipy/scipy#26433

  11. lucascolley commented on Oct 17, 2026

    @lucascolley
    Author

    looks green, @rgommers reckon we can merge the linked PR and close this?

  12. rgommers commented on Oct 18, 2026

    @rgommers
    Member

    Yay, thanks everyone! Bumps to pkgconf 3.0.7.post0 are merged for SciPy, and I think @mhsmith's diagnosis was right.

    I do have a feeling we'll be revisiting this once more at some point, but I can't quite put my finger on it right now, and the observable problem seems gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions