Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

macOS build instructions depend on Homebrew specific configuration #1059

Closed
erlend-aasland opened this issue Feb 27, 2023 · 8 comments
Closed
Assignees

Comments

@erlend-aasland
Copy link
Contributor

Comment by Ned in PR #1058:

I like this approach but, as I've just discovered, Homebrew has just changed the game again by making their tcl-tk formula no longer "keg-only". As noted here, we should re-think this a bit in that light. I'll have some more thoughts on it soon.

Originally posted by @ned-deily in #1058 (comment)

@erlend-aasland
Copy link
Contributor Author

Blocks #1058

@abdnafees
Copy link
Contributor

I can work on this one, I am on macOS.

@CAM-Gerlach
Copy link
Member

Seems like this is pending additional analysis by @ned-deily , so I'm not sure there's anything to be done at the moment, @abdnafees ?

@erlend-aasland
Copy link
Contributor Author

erlend-aasland commented Mar 10, 2023

FTR, since it is not explicitly noted already:

The devguide build instructions currently manipulates PKG_CONFIG_PATH, and then incorrectly assumes it is set in the subshells on the same line. Condense example, as shown by Ned in a related issue or PR (I don't have the link at hand):

$ PKG_CONFIG_PATH="$(brew --prefix tcl-tk)/lib/pkgconfig" echo $(pkg-config --libs tcl tk)
Package tcl was not found in the pkg-config search path.
Perhaps you should add the directory containing `tcl.pc'
to the PKG_CONFIG_PATH environment variable
No package 'tcl' found
Package tk was not found in the pkg-config search path.
Perhaps you should add the directory containing `tk.pc'
to the PKG_CONFIG_PATH environment variable
No package 'tk' found

This is not an issue right now, since Homebrew changed their behaviour (also noted by Ned). But it may be an issue if Homebrew changes their behaviour again.

As a first step, we could inline the PGK_CONFI_PATH manipulations into the subshells. Verbose, yes, but it will be correct and safe.

@abdnafees
Copy link
Contributor

Everything went over my head.

@CAM-Gerlach
Copy link
Member

CAM-Gerlach commented Mar 13, 2023

@abdnafees Given that and considering that the experts @ned-deily and @erlend-aasland have been taking care of this one, you might want to consider helping with a more accessible issue for a new contributor—there are plenty with a Help Wanted label, as well as others on the main CPython repo and others.

@abdnafees
Copy link
Contributor

@CAM-Gerlach Thank you so much. I will check them out.

@erlend-aasland
Copy link
Contributor Author

As per the current recommendation, there's nothing to be done here anymore.

@erlend-aasland erlend-aasland closed this as not planned Won't fix, can't repro, duplicate, stale Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants