summaryrefslogtreecommitdiffstats
path: root/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
...
* bpo-36721: Add --embed option to python-config (GH-13500)Victor Stinner2019-05-231-1/+1
| | | | | | | | | | | | | | | | | | | | | To embed Python into an application, a new --embed option must be passed to "python3-config --libs --embed" to get "-lpython3.8" (link the application to libpython). To support both 3.8 and older, try "python3-config --libs --embed" first and fallback to "python3-config --libs" (without --embed) if the previous command fails. Add a pkg-config "python-3.8-embed" module to embed Python into an application: "pkg-config python-3.8-embed --libs" includes "-lpython3.8". To support both 3.8 and older, try "pkg-config python-X.Y-embed --libs" first and fallback to "pkg-config python-X.Y --libs" (without --embed) if the previous command fails (replace "X.Y" with the Python version). On the other hand, "pkg-config python3.8 --libs" no longer contains "-lpython3.8". C extensions must not be linked to libpython (except on Android, case handled by the script); this change is backward incompatible on purpose. "make install" now also installs "python-3.8-embed.pc".
* bpo-31904: Add posix module support for VxWorks (GH-12118)pxinwr2019-05-211-1/+1
|
* bpo-36618: Don't add -fmax-type-align=8 flag for clang (GH-13320)Victor Stinner2019-05-141-20/+0
| | | | | Python 3.8 now respects the x86-64 ABI: memory allocations are aligned on 16 bytes. The clang flag was only used as a temporary workaround.
* bpo-34602: Avoid failures setting macOS stack resource limit (GH-13011)Ned Deily2019-04-291-6/+0
| | | | | | | | | | | | Under some conditions the earlier fix for bpo-18075, "Infinite recursion tests triggering a segfault on Mac OS X", now causes failures on macOS when attempting to change stack limit with resource.setrlimit resource.RLIMIT_STACK, like regrtest does when running the test suite. The reverted change had specified a non-default stack size when linking the python executable on macOS. As of macOS 10.14.4, the previous code causes a hard failure when running tests, although similar failures had been seen under some conditions under some earlier systems. For now, revert the original change and resume using the default stack size when linking the interpreter.
* bpo-21536: On Android, C extensions are linked to libpython (GH-12989)xdegaye2019-04-291-0/+8
|
* bpo-36722: Don't define ALT_SOABI for Py_TRACE_REFS build (GH-12973)Victor Stinner2019-04-261-1/+2
| | | | Py_TRACE_REFS ABI is incompatible with release and debug (Py_DEBUG) ABI.
* bpo-36722: Debug build loads libraries built in release mode (GH-12952)Victor Stinner2019-04-251-0/+8
| | | | In debug build, import now also looks for C extensions compiled in release mode and for C extensions compiled in the stable ABI.
* bpo-36465: Make release and debug ABI compatible (GH-12615)Victor Stinner2019-04-241-2/+15
| | | | | | | | | | | | | | Release build and debug build are now ABI compatible: the Py_DEBUG define no longer implies Py_TRACE_REFS define which introduces the only ABI incompatibility. A new "./configure --with-trace-refs" build option is now required to get Py_TRACE_REFS define which adds sys.getobjects() function and PYTHONDUMPREFS environment variable. Changes: * Add ./configure --with-trace-refs * Py_DEBUG no longer implies Py_TRACE_REFS
* bpo-36707: Remove the "m" flag (pymalloc) from SOABI (GH-12931)Victor Stinner2019-04-241-3/+3
| | | | | | "./configure --with-pymalloc" no longer adds the "m" flag to SOABI (sys.implementation.cache_tag). Enabling or disabling pymalloc has no impact on the ABI.
* bpo-36618: Don't add -fmax-type-align flag to old clang (GH-12811)Victor Stinner2019-04-121-2/+7
|
* bpo-36618: Add -fmax-type-align=8 flag for clang (GH-12809)Victor Stinner2019-04-121-13/+28
| | | | | | | | | | | | | | Add -fmax-type-align=8 to CFLAGS when clang compiler is detected. The pymalloc memory allocator aligns memory on 8 bytes. On x86-64, clang expects alignment on 16 bytes by default and so uses MOVAPS instruction which can lead to segmentation fault. Instruct clang that Python is limited to alignemnt on 8 bytes to use MOVUPS instruction instead: slower but don't trigger a SIGSEGV if the memory is not aligned on 16 bytes. Sadly, the flag must be expected to CFLAGS and not just CFLAGS_NODIST, since third party C extensions can have the same issue.
* bpo-36588: On AIX, remove major version from sys.platform (GH-12787)Michael Felt2019-04-121-0/+1
| | | | | | On AIX, sys.platform doesn't contain the major version anymore. Always return 'aix', instead of 'aix3' .. 'aix7'. Since older Python versions include the version number, it is recommended to always use sys.platform.startswith('aix').
* bpo-36605: make tags: parse Modules/_io directory (GH-12789)Victor Stinner2019-04-111-2/+2
| | | | "make tags" and "make TAGS" now also parse Modules/_io/*.c and Modules/_io/*.h.
* bpo-31904: Add cross-build support for VxWorks RTOS (GH-11968)pxinwr2019-02-271-2/+19
|
* closes bpo-13497: Fix `broken nice` configure test. (GH-12041)ngie-eign2019-02-261-0/+2
| | | | | Per POSIX, `nice(3)` requires `unistd.h` and `exit(3)` requires `stdlib.h`. Fixing the test will prevent false positives with pedantic compilers like clang.
* bpo-12822: use monotonic clock for condvar if possible (GH-11723)Inada Naoki2019-02-201-1/+2
|
* bpo-35903: Use autoconfig to probe for shm_open() and shm_unlink(). (#11765)Neil Schemenauer2019-02-081-0/+24
| | | | | | Use autoconfig to probe for shm_open() and shm_unlink(). Set SHM_NEEDS_LIBRT if we must link with librt to get the shm_* functions. Change setup.py to use the autoconfig defines. These changes should make it more likely that _multiprocessing/posixshmem.c gets built correctly on different platforms.
* bpo-35520: Fix build with dtrace support on certain systems. (#11194)Jakub Kulík2019-01-241-1/+1
|
* bpo-35674: Add os.posix_spawnp() (GH-11554)Joannah Nanjekye2019-01-161-1/+1
| | | Add a new os.posix_spawnp() function.
* bpo-28503: Use crypt_r() when available instead of crypt() (GH-11373)Gregory P. Smith2018-12-301-0/+17
| | | | | Use crypt_r() when available instead of crypt() in the crypt module. As a nice side effect: This also avoids a memory sanitizer flake as clang msan doesn't know about crypt's internal libc allocated buffer.
* bpo-35257: Avoid leaking LTO linker flags into distutils (GH-10900)stratakis2018-12-191-1/+2
| | | | | | When compiling 3rd party C extensions, the linker flags used by the compiler for the interpreter and the stdlib modules, will get leaked into distutils. In order to avoid that, the PY_CORE_LDFLAGS and PY_LDFLAGS_NODIST are introduced to keep those flags separated.
* bpo-35351: Pass link time optimization flags to CFLAGS_NODIST (GH-10797)stratakis2018-12-041-1/+1
| | | | | | When using link time optimizations, the -flto flag is passed to BASECFLAGS, which makes it propagate to distutils. Those flags should be reserved for the interpreter and the stdlib extension modules only, thus moving those flags to CFLAGS_NODIST.
* bpo-35214: Initial clang MemorySanitizer support (GH-10479)Gregory P. Smith2018-11-121-1/+27
| | | | | | | | | | Adds configure flags for msan and ubsan builds to make it easier to enable. These also encode the detail that address sanitizer and memory sanitizer should disable pymalloc. Define MEMORY_SANITIZER when appropriate at build time and adds workarounds to existing code to mark things as initialized where the sanitizer is otherwise unable to determine that. This lets our build succeed under the memory sanitizer. not all tests pass without sanitizer failures yet but we're in pretty good shape after this.
* bpo-28015: Support LTO build with clang (GH-9908)serge-sans-paille2018-10-241-19/+48
| | | | | | | | | | .o generated by clang in LTO mode actually are LLVM bitcode files, which leads to a few errors during configure/build step: - add lto flags to the BASECFLAGS instead of CFLAGS, as CFLAGS are used to build autoconf test case, and some are not compatible with clang LTO (they assume binary in the .o, not bitcode) - force llvm-ar instead of ar, as ar is not aware of .o files generated by clang -flto
* closes bpo-34869: Remove LDLAST. (GH-9667)Benjamin Peterson2018-10-041-2/+0
|
* bpo-31425: Expose AF_QIPCRTR in socket module (GH-3706)Bjorn Andersson2018-09-261-0/+10
| | | | | | The AF_QIPCRTR address family was introduced in Linux v4.7. Co-authored-by: Bjorn Andersson <bjorn.andersson@linaro.org>
* closes bpo-34585: Don't do runtime test to get float byte order. (GH-9085)Ross Burton2018-09-191-63/+13
| | | | | | | Currently configure.ac uses AC_RUN_IFELSE to determine the byte order of doubles, but this silently fails under cross compilation and Python doesn't do floats properly. Instead, steal a macro from autoconf-archive which compiles code using magic doubles (which encode to ASCII) and grep for the representation in the binary. RFC because this doesn't yet handle the weird ancient ARMv4 OABI 'mixed-endian' encoding properly. This encoding is ancient and I don't believe the union of "Python 3.8 users" and "OABI users" has anything in. Should the support for this just be dropped too? Alternatively, someone will need to find an OABI toolchain to verify the encoding of the magic double.
* bpo-33486: regen autotools files using autoupdate+autoreconf (GH-6853)Eitan Adler2018-09-141-4/+4
|
* Don't run AC_STRUCT_TIMEZONE twice. (GH-9305)Benjamin Peterson2018-09-141-5/+0
|
* bpo-34674: Assume unistd.h exists on Unix. (GH-9290)Benjamin Peterson2018-09-141-1/+1
|
* bpo-34652: Remove lchmod from the big func checking block. (GH-9247)Benjamin Peterson2018-09-131-2/+2
| | | | A fix for 883702ebb8bbfa749ef0040d1b58d6222bf589ee.
* closes bpo-34652: Always disable lchmod on Linux. (GH-9234)Benjamin Peterson2018-09-121-0/+7
|
* closes bpo-34640: Remove the TANH_PRESERVES_ZERO_SIGN configure check. (GH-9206)Benjamin Peterson2018-09-121-27/+0
|
* Remove configure check LOG1P_DROPS_ZERO_SIGN. (GH-9193)Benjamin Peterson2018-09-111-30/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is unused. <!-- Thanks for your contribution! Please read this comment in its entirety. It's quite important. # Pull Request title It should be in the following format: ``` bpo-NNNN: Summary of the changes made ``` Where: bpo-NNNN refers to the issue number in the https://bugs.python.org. Most PRs will require an issue number. Trivial changes, like fixing a typo, do not need an issue. # Backport Pull Request title If this is a backport PR (PR made against branches other than `master`), please ensure that the PR title is in the following format: ``` [X.Y] <title from the original PR> (GH-NNNN) ``` Where: [X.Y] is the branch name, e.g. [3.6]. GH-NNNN refers to the PR number from `master`. -->
* bpo-33625: Release GIL for grp.getgr{nam,gid} and pwd.getpw{nam,uid} (GH-7081)William Grzybowski2018-09-071-1/+2
| | | | | | Release GIL on grp.getgrnam(), grp.getgrgid(), pwd.getpwnam() and pwd.getpwuid() if reentrant variants of these functions are available. Patch by William Grzybowski.
* bpo-34448: Improve output of usable wchar_t check (GH-8846)Michael Osipov2018-08-241-3/+3
|
* bpo-34412: Make signal.strsignal() work on HP-UX (GH-8786)Michael Osipov2018-08-231-1/+1
| | | | | | Introduce a configure check for strsignal(3) which defines HAVE_STRSIGNAL for signalmodule.c. Add some common signals on HP-UX. This change applies for Windows and HP-UX.
* bpo-30411: Use --git-dir instead of -C to make git work under version below ↵Xiang Zhang2018-08-201-3/+3
| | | | 1.8.5. (GH-8744)
* bpo-32430: Rename Modules/Setup.dist to Modules/Setup (GH-8229)Antoine Pitrou2018-07-161-7/+1
| | | | | bpo-32430: Rename Modules/Setup.dist to Modules/Setup Remove the necessity to copy the former manually to the latter when updating the local source tree.
* bpo-34121: Fix detection of C11 atomic support on clang. (GH-8288)Benjamin Peterson2018-07-161-2/+1
|
* bpo-33648: Remove PY_WARN_ON_C_LOCALE (GH-7114)Eitan Adler2018-07-111-17/+0
| | | | This code does not appear to be used anywhere in the python code base. The use was removed in eb81795d7d3a8c898fa89.
* bpo-30345: Add -g to LDFLAGS for LTO (GH-7709)Victor Stinner2018-06-191-0/+8
| | | Add -g to LDFLAGS when compiling with LTO to get debug symbols.
* bpo-32493: Correct test for uuid_enc_be availability in configure.ac. ↵Ned Deily2018-06-091-3/+1
| | | | (GH-7511) (GH-7567)
* bpo-5755: Move -Wstrict-prototypes to CFLAGS_NODIST (GH-7395)INADA Naoki2018-06-051-5/+20
|
* Docs: fix some wrong words (GH-6987)Eitan Adler2018-06-021-2/+2
| | | Fix typos in code comments: bdb.py and configure.ac.
* bpo-32493: Fix uuid.uuid1() on FreeBSD. (GH-7099)Serhiy Storchaka2018-05-241-0/+15
| | | Use uuid_enc_be() if available to encode UUID to bytes as big endian.
* closes bpo-33512: use standard for detecting long double (GH-6847)Eitan Adler2018-05-161-9/+1
|
* bpo-33483: more correctly handle finding the C compiler (GH-6780)Eitan Adler2018-05-151-38/+0
| | | | | | | | | Instead of passing configure args such as --without-gcc or --with-icc, instead prefer to rely on the native way of finding the compiler: passing CC (or CPP or CXX depending). This allows configure to find the correct compiler instead of having to be explicitly told. It also more correctly builds on both macOS and FreeBSD since the system compiler is used by default (cc)
* bpo-33332: Add signal.valid_signals() (GH-6581)Antoine Pitrou2018-05-041-1/+1
|
* bpo-33377: add triplets for mips-r6 and riscv (#6655)Matthias Klose2018-04-301-0/+28
| | | | | | * issue33377: add triplets for mips-r6 and riscv * issue33377: add triplets for mips-r6 and riscv (NEWS entry)
generated by cgit v0.12 at 2024-12-02 20:28:09 (GMT)