@tonybaloney: thanks for the first 30 commits, I built on that to remove the tklib library

The recipe is failing with

==> brew linkage --test pypy3.8
==> FAILED
Full linkage --test pypy3.8 output
Truncated linkage --test pypy3.8 output
  Error: Broken dependencies:
    /opt/homebrew/opt/tcl-tk/lib/libtcl8.6.dylib (tcl-tk)
    /opt/homebrew/opt/tcl-tk/lib/libtk8.6.dylib (tcl-tk)

but there should be no use of libtcl in the recipe. How can I find out what is going on?

The recipe is failing with

==> brew linkage --test pypy3.8
==> FAILED
Full linkage --test pypy3.8 output
Truncated linkage --test pypy3.8 output
  Error: Broken dependencies:
    /opt/homebrew/opt/tcl-tk/lib/libtcl8.6.dylib (tcl-tk)
    /opt/homebrew/opt/tcl-tk/lib/libtk8.6.dylib (tcl-tk)

but there should be no use of libtcl in the recipe. How can I find out what is going on?

My understanding of the issue is that PyPy will link to TCL-TK if it is installed, regardless of whether the environment variable is set. https://foss.heptapod.net/pypy/pypy/-/blob/branch/default/lib_pypy/_tkinter/tklib_build.py#L22-28

The issue you're seeing in the build means that PyPy has linked to TCL-TK when it was installed as a dependency of another package (which it shouldn't).

The environment variable, PYPY_PACKAGE_WITHOUTTK only seems to impact Windows builds looking at the source and how options.no__tkinter is used https://foss.heptapod.net/pypy/pypy/-/blob/branch/default/pypy/tool/release/package.py

There is additional logic to skip package building when the no_<package> option is set. Is there a way to increase verbosity and/or run the recipe locally?

There is additional logic to skip package building when the no_ option is set. Is there a way to increase verbosity and/or run the recipe locally?

brew install --debug --verbose <package> is the most verbose you can get.

Just keep tklib, TBH. I'm not sure it's worth the effort trying to excise it.

While you're at it, could you try to clean up your branch a little? At minimum, each commit should modify at most one formula at a time.

Finally, let's not delete pypy3. I suggest renaming it to pypy3.7 and adding a pypy3 alias pointing to pypy3.9.

Just keep tklib, TBH. I'm not sure it's worth the effort trying to excise it.

That was where #117699 ended up. But it seems there is no way to use the homebrew tk/tcl libraries in a recipe. Is there a way to fix that?

I'm not sure I understand -- the linkage failure is precisely because the build is using Homebrew tcl-tk, so trying to use it is broken because Homebrew tcl-tk is not installed.

When installing homebrew tcl-tk, the build complains

Dependency 'tcl-tk' is provided by macOS; please replace 'depends_on' with 'uses_from_macos'

But when using macos tcl-tk, there is an error about missing X11 headers

In file included from _tkinter/__pycache__/_cffi__gd50bda0axe0f95f31.c:56:
  /Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk/usr/include/tk.h:86:11: \
    fatal error: 'X11/Xlib.h' file not found
  #       include <X11/Xlib.h>

I don't have MacOSX13 headers on my machine. I do have MacOSX11.3, MacOSX12.1, and MacOSX12.3, and all those have X11 headers.

When installing homebrew tcl-tk, the build complains

Dependency 'tcl-tk' is provided by macOS; please replace 'depends_on' with 'uses_from_macos'

That's fine. We can ignore that failure because we know the system one doesn't work.

We can ignore that failure

Such a fix would allow #117699 to pass tests, and then I can close this PR.

@carlocab what is the incantation to ignore the "Dependency 'tcl-tk' is provided by macOS; please replace 'depends_on' with 'uses_from_macos'" error?

Just leave it be; we can merge this if that's the only error.

Please do clean up your branch though.

Such a fix would allow #117699 to pass tests, and then I can close this PR.

Linux build failed in the previous PR.

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.