native-api

Okay, I see that this can happen legitimately, if you're overwriting the environment with `-f`.

This looks like MacOS' antivirus falsely detecting these files. Similar problems were reported before. A common solution was to reinstall Homebrew, to clear the antivirus' saved heuristics on it. https://github.com/pyenv/pyenv/issues/2623#issuecomment-1436006967:...

Without diagnostic information as per the issue template, we cannot say anything specific.

@nolafs This is a different issue, listed in common build problems: https://github.com/pyenv/pyenv/wiki/Common-build-problems#on-apple-silicon-when-building-for-arm64-a-dependency-is-present-in-x64-homebrew-but-not-arm64-homebrew

> ### Features > > * `pyenv local system` -> if system is installed, removes existing .py-env.version if it exists printing the previous version Introduces ambiguity (which violates Python Zen...

I really don't like the idea of having to supply an argument via an envvar -- but can't readily recall anything better. I guess we should do a brainstorm in...

Got a nice-looking idea of how to couple a version and its alias: with a colon separator. A colon shouldn't normally be present in directory names (which Pyenv-managed installation names...

> We can probably test this in the same test that tests `PACKAGE_CFLAGS`. ...And my memory fails me here, too: there is no such test. There is however `"yaml is...

Superseded by https://github.com/pyenv/pyenv/pull/3130

Looks like you have compiler-affecting envvars set with shell special characters (like newlines) that mess up the command lines. ``` configure:5108: checking whether the C compiler works configure:5130: gcc -I/mnt/storage/home/schmeing/.pyenv/versions/3.12.1/include...