Building fails with "./configure: line 5177: 5: Bad file descriptor" on almalinux 9.3 about pyenv HOT 7 OPEN

I've got this problem on RHEL8.

• It works after downgrading samba to 4.17.5-3
• It also works on samba 4.18.6-3 when restricting the passwd entry in /etc/nsswitch.conf to just files.

from pyenv.

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 -L/mnt/storage/home/schmeing/.pyenv/versions/3.12.1/lib -Wl,-rpath,/mnt/storage/home/schmeing/.pyenv/versions/3.12.1/lib conftest.c -L/mnt/storage/home/schmeing/.pyenv/versions/3.12.1/lib -Wl,-rpath,/mnt/storage/home/schmeing/.pyenv/versions/3.12.1/lib >&5
configure:5134: $? = 1
configure:5174: result: no
configure: failed program was:
configure:5179: error: in `/mnt/storage/home/schmeing/src/python-build.20240205143045.381288/Python-3.12.1':
configure:5181: error: C compiler cannot create executables
See `config.log' for more details

from pyenv.

Hi,

I'm a co-worker with the same problem and I doubt it's an environmental variable. Since running the ./configure script with the same arguments from the same shell works fine it looks something is different in the invocation of the ./configure script, which makes our python build fail.

I'm concentrating on the "bad file descriptor" error and quickly made a patch which modifies the configure script to show it's file descriptors right at the beginning by adding ls -l /proc/$$/fd. If I run it through a shell directly it shows

lrwx------ 1 pytest test 64  6. Feb 08:20 0 -> /dev/pts/0
lrwx------ 1 pytest test 64  6. Feb 08:20 1 -> /dev/pts/0
lrwx------ 1 pytest test 64  6. Feb 08:20 2 -> /dev/pts/0
lr-x------ 1 pytest test 64  6. Feb 08:20 255 -> /tmp/python-build.20240206081830.419504/Python-3.10.13/configure

while running it through pyenv gives me

lr-x------ 1 pytest test 64  6. Feb 08:30 0 -> pipe:[1211642]
lrwx------ 1 pytest test 64  6. Feb 08:30 1 -> /tmp/python-build.20240206083036.421464.log
lrwx------ 1 pytest test 64  6. Feb 08:30 2 -> /tmp/python-build.20240206083036.421464.log
lr-x------ 1 pytest test 64  6. Feb 08:30 255 -> /tmp/python-build.20240206083036.421464/Python-3.10.13/configure
lrwx------ 1 pytest test 64  6. Feb 08:30 3 -> /dev/pts/0
lrwx------ 1 pytest test 64  6. Feb 08:30 4 -> /tmp/python-build.20240206083036.421464.log

Marius

from pyenv.

I'm concentrating on the "bad file descriptor" error and quickly made a patch which modifies the configure script to show it's file descriptors

That should help!

Descriptor 5 is supposed to point to config.log. Something probably goes wrong while opening it.

Seeing descriptors before and after the code line on the link should help to understand what's happening. As should adding set -x to configure.

So far, this seems to be something unconnected to Pyenv's logic -- something like system permissions and/or resource limits.

from pyenv.

https://bugzilla.samba.org/show_bug.cgi?id=15464 looks terribly suspicious. Should be fixed in samba-4.18.7 and samba-4.19.1.

from pyenv.

I've got this problem on RHEL9, but Im not really in a position to downgrade samba.

Is there another workaround?

from pyenv.

I've got this problem on RHEL9, but Im not really in a position to downgrade samba.

Is there another workaround?

Build the codebase with the fix and UPgrade it?

from pyenv.