native-api

@HideNameUser okay, the faulty line is output by the generated `config.status` script in the build tree. Please attach that file and its debug trace (the output of `export PS4='+(${BASH_SOURCE}:${LINENO}): ${FUNCNAME[0]:+${FUNCNAME[0]}():...

> Looks like it doesn't output anything to `pyconfig.h` for some reason. A likely reason is some standard UNIX utility is shadowed by some 3rd-party software on your system, causing...

@krmao Pleasew provide the information requested at https://github.com/pyenv/pyenv/issues/3062#issuecomment-2401112141 for me to be able to say anything

> how to attach that file? do you have steps to do this? @native-api > > ``` > ➜ ~ export PS4='+(${BASH_SOURCE}:${LINENO}): ${FUNCNAME[0]:+${FUNCNAME[0]}(): }'; bash -x ./config.status > bash: ./config.status:...

> ```shell > + eval '$AWK -f "$ac_tmp/defines.awk"' ' '\''pyconfig.h.in'\''' > ++ awk -f ./confxRYd6w/defines.awk pyconfig.h.in > + diff pyconfig.h ./confxRYd6w/config.h > ``` This is where it goes wrong. Need...

Superseded by https://github.com/pyenv/pyenv/pull/3136 and https://github.com/pyenv/pyenv/pull/3151

WFM in MacOS 12. May be an upstream issue, try with the newest snapshot. If that doesn't help, find `libpython*.a` in the build directory and try to find the mission...

`config.log` as requested in the issue template would've clarified the concerns in the last paragraph.

> 2\. Fix the wonky linker code to only include the path to the newly-compiled static library, and not the path to the installed version. I have an idea how...

It's not so simple, as it turns out. We do need `-L/lib` in LDFLAGS _for Python extensions._ We do add them to LIBS though -- maybe that'll be enough. Need...