Too many issues will kill our team's development velocity, drastically.
Make sure you have checked all steps below.

Prerequisite

• Make sure your problem is not listed in the common build problems.
• Make sure no duplicated issue has already been reported in the pyenv issues. You should look for closed issues, too.
• Make sure you are not asking us to help solving your specific issue.
  • GitHub issues is opened mainly for development purposes. If you want to ask someone to help solving your problem, go to some community site like Gitter, StackOverflow, etc.
• Make sure your problem is not derived from packaging (e.g. Homebrew).
  • Please refer to the package documentation for the installation issues, etc.
• Make sure your problem is not derived from plugins.
  • This repository is maintaining pyenv and the default python-build plugin only. Please refrain from reporting issues of other plugins here.

Description

• Platform information (e.g. Ubuntu Linux 16.04): Arch
• OS architecture (e.g. amd64): x86_64
• pyenv version: 2.4.17
• Python version: any version CPython I tried to install failed, this example is about v3.10.15
• C Compiler information (e.g. gcc 7.3): gcc 14.2.1 20240910
• Please attach the debug trace of the failing command as a gist:
  • Run env PYENV_DEBUG=1 <faulty command> 2>&1 | tee trace.log and attach trace.log. E.g. if you have a problem with installing Python, run env PYENV_DEBUG=1 pyenv install -v <version> 2>&1 | tee trace.log (note the -v option to pyenv install).
• If you have a problem with installing Python, please also attach config.log from the build directory
  • The build directory is reported after the "BUILD FAILED" message and is usually under /tmp.
• If the build succeeds but the problem is still with the build process (e.g. the resulting Python is missing a feature), please attach
  • the debug trace from reinstalling the faulty version with env PYENV_DEBUG=1 pyenv install -f -k -v <version> 2>&1 | tee trace.log
  • config.log from the build directory. When using pyenv install with -k as per above, the build directory will be under $PYENV_ROOT/sources.

Hi,

After many hours trying to fix my problem without success, I hope you will be able to help me.

Overview:

More details in this gist

Basically, I encounter this error:

$ pyenv install 3.10
Downloading Python-3.10.15.tar.xz...
-> https://www.python.org/ftp/python/3.10.15/Python-3.10.15.tar.xz
Installing Python-3.10.15...

BUILD FAILED (Arch Linux using python-build 20180424)

Inspect or clean up the working tree at /tmp/python-build.20241101205203.9933
Results logged to /tmp/python-build.20241101205203.9933.log

Last 10 log lines:
./configure: line 3936: 5: Bad file descriptor
./configure: line 3936: 5: Bad file descriptor
./configure: line 3936: 5: Bad file descriptor
./configure: line 3936: 5: Bad file descriptor
checking whether the C compiler works... ./configure: line 3983: 5: Bad file descriptor
no
./configure: line 4026: 5: Bad file descriptor
configure: error: in `/tmp/python-build.20241101205203.9933/Python-3.10.15':
configure: error: C compiler cannot create executables
See `config.log' for more details

What I tried:

• used both pyenv-installer and the official arch package
• installed the build dependencies read the whole wiki and searched the existing issues
• used a default location ($HOME/<user>/.pyenv, as well as a custom one (mnt/cache/apps/pyenv)
• checked the existing issues on this repo, and the CPython one
  • in particular, I noticed this issue: Building fails with "./configure: line 5177: 5: Bad file descriptor" on almalinux 9.3 #2895
    • but it didn't help (this bug related to Samba was closed more than a year ago, and my version is v4.21.1)

Reading these 2 comments (1 and 2), I fully understand my issue is linked to the compiler so I also:

• ensured no env var may impact GCC, according to this page on gnu.org
• tried to run ./configure directly from the folder (it works)
• reinstall the relevant packages, tried to increase the limit of opened files, tried with a different compiler (GCC 13, clang) -> no change
• I never use gcc myself, so it's quite unlikely I messed with its config or so

Conclusions:

I'm sorry to bother you with that issue that is probably not linked to pyenv directly, but I would be very grateful if you can help me, or guide me to investigate further, as I must admit I'm a bit lost...

Thanks in advance for help.