Skip to content

macOS build instructions depend on Homebrew specific configuration #1059

Description

@erlend-aasland

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)

Activity

  1. erlend-aasland commented on Feb 27, 2023

    @erlend-aasland
    ContributorAuthor

    Blocks #1058

  2. abdnafees commented on Mar 10, 2023

    @abdnafees
    Contributor

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

  3. CAM-Gerlach commented on Mar 10, 2023

    @CAM-Gerlach
    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 ?

  4. erlend-aasland commented on Mar 10, 2023

    @erlend-aasland
    ContributorAuthor

    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.

  5. abdnafees commented on Mar 12, 2023

    @abdnafees
    Contributor

    Everything went over my head.

  6. CAM-Gerlach commented on Mar 13, 2023

    @CAM-Gerlach
    Member

    @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.

  7. abdnafees commented on Mar 13, 2023

    @abdnafees
    Contributor

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

  8. erlend-aasland commented on Jun 8, 2023

    @erlend-aasland
    ContributorAuthor

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

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

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions