m/pyenv
1
0
Fork 0
mirror of https://github.com/pyenv/pyenv.git synced 2025-11-12 21:33:54 -05:00
Code Wiki Activity

Updated Common build problems (markdown)

native-api
2023-04-06 05:42:45 +03:00
parent 95add4730c
commit 70a94555d2
1 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
Common-build-problems.md

@@ -349,7 +349,12 @@ This means that *the Python version you're installing doesn't support your MacOS
## Keg-only Homebrew packages are forcibly linked / added to PATH ## Keg-only Homebrew packages are forcibly linked / added to PATH
Some Homebrew packages are installed as "keg-only" -- i.e. their executables are not linked to `$(brew --prefix)/bin`. Some Homebrew packages are installed as "keg-only" -- i.e. their executables are not linked to `$(brew --prefix)/bin`.
This is typically done because then they would override stock MacOS software (the specific reason is mentioned in `brew info` output), causing breakages. The same happens if you manually add them to PATH as specified in their `brew info` output. This is typically done because then they would override stock MacOS software (the specific reason is mentioned in `brew info` output), causing breakages. The same happens if you manually add them to `PATH` as specified in their `brew info` output.
In particular, these Homebrew packages are known to break Pyenv builds if added to `PATH`: `binutils`, `llvm`. In particular, these Homebrew packages are known to break Pyenv builds if added to `PATH` (with known error messages they cause in the build log):
`coreutils` only causes breakage if non-prefixed executables are added to `PATH`.
* `binutils`
* `configure: error: Unexpected output of 'arch' on OSX`
* `llvm`
* `warning: pointer is missing a nullability type specifier`
* `coreutils` only causes breakage if non-prefixed executables are added to `PATH`.