Bug report
Bug description:
We mess up EXEEXT in configure.ac:
|
AC_MSG_CHECKING([for --with-suffix]) |
|
AC_ARG_WITH([suffix], |
|
[AS_HELP_STRING([--with-suffix=SUFFIX], [set executable suffix to SUFFIX (default is empty, yes is mapped to '.exe')])], |
|
[ |
|
AS_CASE([$with_suffix], |
|
[no], [EXEEXT=], |
|
[yes], [EXEEXT=.exe], |
|
[EXEEXT=$with_suffix] |
|
) |
|
], [ |
|
AS_CASE([$ac_sys_system/$ac_sys_emscripten_target], |
|
[Emscripten/browser*], [EXEEXT=.js], |
|
[Emscripten/node*], [EXEEXT=.js], |
|
[WASI/*], [EXEEXT=.wasm], |
|
[EXEEXT=] |
|
) |
|
]) |
|
AC_MSG_RESULT([$EXEEXT]) |
This creates problems1, since AX_C_FLOAT_WORDS_BIGENDIAN expects EXEEXT and ac_exeext to be the same. EXEEXT and ac_exeext are set up by AC_PROG_CC:
We can mitigate this by:
- setting
ac_exeext=$EXEEXT after L1340 in configure.ac
- use another variable than
EXEEXT; for example EXE_SUFFIX
- other workarounds?
My gut feel regarding these is that I'd really not like to add more EXEEXT hacks, so I'd like to avoid 1). 2) should be ok, given that no-one else are depending on EXEEXT (cc. @hroncok).
CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux, macOS, Other
Linked PRs
Bug report
Bug description:
We mess up
EXEEXTinconfigure.ac:cpython/configure.ac
Lines 1323 to 1340 in cda0ec8
This creates problems1, since
AX_C_FLOAT_WORDS_BIGENDIANexpectsEXEEXTandac_exeextto be the same.EXEEXTandac_exeextare set up byAC_PROG_CC:cpython/configure.ac
Line 1026 in cda0ec8
We can mitigate this by:
ac_exeext=$EXEEXTafter L1340 inconfigure.acEXEEXT; for exampleEXE_SUFFIXMy gut feel regarding these is that I'd really not like to add more
EXEEXThacks, so I'd like to avoid 1). 2) should be ok, given that no-one else are depending onEXEEXT(cc. @hroncok).CPython versions tested on:
CPython main branch
Operating systems tested on:
Linux, macOS, Other
Linked PRs
Footnotes
https://github.com/python/cpython/pull/125571#issuecomment-2422385731, https://github.com/python/cpython/pull/125571#issuecomment-2422414137 ↩