| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Should it be documented in https://docs.python.org/dev/using/configure.html? |
Sorry, something went wrong.
|
This PR should fix the 3 wasm32-emscripten buildbots. See: |
Sorry, something went wrong.
|
!buildbot wasm32-emscripten |
Sorry, something went wrong.
|
🤖 New build scheduled with the buildbot fleet by @vstinner for commit bed957b 🤖 The command will test the builders whose names match following regular expression: wasm32-emscripten The builders matched are:
|
Sorry, something went wrong.
|
The "Configure host Python" step now says no for libatomic, as expected, good!
checking whether libatomic is needed by <pyatomic.h>... no
checking whether libatomic is needed by <pyatomic.h>... no
checking whether libatomic is needed by <pyatomic.h>... no |
Sorry, something went wrong.
|
test_threading failed on Windows x64: it's an unrelated known bug, see: #108987 (I proposed a fix). I re-ran the Windows x64 job. |
Sorry, something went wrong.
configure no longer uses libatomic by default when Python is
cross-compiled. The LIBATOMIC variable can be set manually in this
case:
./configure LIBATOMIC="-latomic" (...)
|
I wrote PR #109224 to document LIBATOMIC and other configuration variables. |
Sorry, something went wrong.
|
LGTM! |
Sorry, something went wrong.
| ]])], | ||
| [ac_cv_libatomic_needed=no], dnl build succeeded | ||
| [ac_cv_libatomic_needed=yes], dnl build failed | ||
| [ac_cv_libatomic_needed=no]) dnl cross compilation |
There was a problem hiding this comment.
We could have used ac_cv_libatomic_needed=n/a for a more accurate result message.
Sorry, something went wrong.
There was a problem hiding this comment.
Oh, I didn't know this value.
Sorry, something went wrong.
There was a problem hiding this comment.
Oh, I didn't know this value.
Actually, the value is up to you; it's not a magical GNU Autoconf value :) See docs for AC_CACHE_CHECK. The signature for that macro is:
AC_CACHE_CHECK (message, cache-id, commands-to-set-it)
Quoting the docs:
It calls AC_MSG_CHECKING for message, then AC_CACHE_VAL with the cache-id and commands arguments, and AC_MSG_RESULT with cache-id.
In out case, cache-id is ac_cv_libatomic_needed. Whatever we set it to will be displayed to the user at the end of the check (via the implicit AC_MSG_RESULT call). So if we set ac_cv_libatomic_needed to n/a, the user should see this when cross-compiling:
checking whether libatomic is needed by <pyatomic.h>... n/a
Currently, the user will see this when cross-compiling:
checking whether libatomic is needed by <pyatomic.h>... no
The "no" may lead the user to incorrectly assume that configure actually checked whether libatomic was needed (and that configure concluded it was not).
I think it may be worth it to adjust this message. What do you think?
Sorry, something went wrong.
There was a problem hiding this comment.
Oh, my suggestion is made moot by #109344
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
configure no longer uses libatomic by default when Python is cross-compiled. The LIBATOMIC variable can be set manually in this case: