| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
newline in configure --help.
|
|
|
|
|
|
|
|
|
| |
disables it. The gc test is moved to just after the thread test, as
is the wctype-functions test.
Modules/Setup.config is generated instead of Modules/Setup.thread.
Applied SF patch #100684 (loewis) to fix help alignment bug.
|
|
|
|
| |
update configure files (turn --with-cycle-gc on for beta release?)
|
|
|
|
|
|
| |
Note that configure hadn't been checked in a few times so it has more
changes, catching up with the last few changes to congifure.in as
well.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
64-bit readiness (the config values are needed for patches that I will
be submitting later today. The changes are as follows:
- add SIZEOF_OFF_T #define's to PC/config.h (it was already in configure.in)
- add SIZEOF_TIME_T #define to PC/config.h and configure
Needed for some buffer overflow checking because sizeof(time_t) is
different on Win64.
- add SIZEOF_FPOS_T #define
Needed for the Win64 large file support implementation.
- add SIZEOF_HKEY in PC/config.h only
Needed for proper Win32 vs. Win64 handling in PC/winreg.c
- #define HAVE_LARGEFILE_SUPPORT for Win64
- typedef long intptr_t; for all Windows except Win64 (which defines it
itself)
This is a new ANSI (I think) type that is useful (and used by me) for
proper handling in msvcrtmodule.c and posixmodule.c
- indent the nested #ifdef's and #defines in PC/config.h
This is *so* much more readable. There cannot be a compiler
compatibilty issue here can there? Perl uses indented #defines and it
compiles with everything.
|
|
|
|
|
|
|
|
|
|
|
| |
threads use --without-threads. No extra tests of thread/compiler
combinations have been added.
--with(out)-thread and --with(out)-threads are completely
interchangeable.
--with-threads still supports the =DIRECTORY option for specifying
where to find thread libraries.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds the openpty() and forkpty() library calls to posixmodule.c,
when they are available on the target
system. (glibc-2.1-based Linux systems, FreeBSD and BSDI at least, probably
the other BSD-based systems as well.)
Lib/pty.py is also rewritten to use openpty when available, but falls
back to the old SGI method or the "manual" BSD open-a-pty
code. Openpty() is necessary to use the Unix98 ptys under Linux 2.2,
or when using non-standard tty names under (at least) BSDI, which is
why I needed it, myself ;-) forkpty() is included for symmetry.
|
| |
|
|
|
|
|
|
| |
create shared extensions rather than 'ld -G'. This ensures that shared
extensions link against libgcc.a, in case there are any functions in the
GCC runtime not already in the Python core.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Some new configuration tests and a new option, --with-wctype-functions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Solaris 2 has stub implementations of the POSIX thread functions such as
pthread_detach in libc. This means that configure tries to use them without
-lpthread, then the test of pthread_create fails and the configuration
falls back to the Solaris thread library. This patch moves the test for
pthread_create in -lpthread ahead of the test for pthread_detach in libc.
The patch also ensures that -lpthread is at the start of the library list
when linking, to pick up POSIX thread semantics for fork (see below).
Justification.
Use of POSIX threads on Solaris ensures that the fork() call only runs the
thread that called fork() in the child. This is desirable to prevent (for
example) parent server or database threads running in the child. Sun's
-lthread library uses a traditional fork() which replicates all the
parent's threads in the child. I find this undesirable.
Digression.
The configure.in seems to always test for -lthread even if a POSIX library
is found. I'm not enough of a configure.in wizard to decide whether this is
desirable or how to fix it. It is also irrelevant to this patch - I just
spotted it while testing.
End of Digression.
|
|
|
|
|
|
| |
needed an adaptation for the latest gcc -- we need to grep stderr as
well as stdout for the magic string BFD. (Does anybody know what BFD
means?)
|
|
|
|
|
|
| |
NOTE: Windows, Mac and OS/2 build procedures must be adapted manually!
This is part of a set of patches by Greg Stein.
|
|
|
|
| |
(The configure script is regenerated, not from his patch.)
|
|
|
|
|
|
|
|
| |
least on Solaris (sometimes it's Unix98, sometimes it conforms to an
early draft).
Properly generate config.h.in using autoheader instead of editing it
manually; thanks, Guido!
|
| |
|
|
|
|
| |
confstr(), and sysconf().
|
| |
|
|
|
|
|
|
|
| |
Duzan, for AIX, to support C++ objects with static initializers, when
using the genuine IBM C++ compiler (namely xlC/xlC_r).
See accompanying patches to acconfig.h and importdl.c.
|
| |
|
| |
|
|
|
|
| |
(My fault, not Dom's -- he submitted a correct patch to configure.)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
donated by David Arnold.
|
|
|
|
| |
doesn't exist and doesn't make sense).
|
|
|
|
|
|
| |
LIBM (from --with-libm=...); this actually broke the customizability
offered by the latter option. Thanks go to Clay Spence for reporting
this.
|
| |
|
|
|
|
| |
for BeOS better.
|
|
|
|
|
|
|
|
|
| |
The following patches (relative to 1.5.2b1) enable Python dynamic
loading to work on NetBSD platforms that use ELF (presnetly mips and
alpha systems). They automaticly determine wether the system is ELF or
a.out rather than using astatic list of platforms so that when other
NetBSD platforms move to ELF, python will continue to work without
change.
|
|
|
|
| |
(Slightly modified to isolate the test for various funcs more.)
|
|
|
|
|
|
| |
- remove PowerPC specific compiler switch for BeOS (Chris Herborth)
- FreeBSD/3 support
- check for pthread_detach in libc instead of _create
|
| |
|
|
|
|
|
|
| |
Added AC_CHECK_SIZEOF(void *).
Added yet another test for pthreads (pthread_create may be in libc).
Added pthread_init to list of functions whose existence is checked.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(1) reorder the tests for -Olimit 1500 and -OPT:Olimit=0 so that the
latter test is performed first, and if it works, the former test is
skipped. This should get rid of the problem that the new SGI
compilers accept both but emit a warning about -Olimit 1500.
(2) The DGUX hack was somehow split in two by the Olimit tests,
probably as the result of a non-context diff. Moved this back
together again, after the Olimit tests.
|
| |
|
| |
|
|
|
|
| |
enough platforms).
|
| |
|
| |
|