remove some unnecessary '#include "confdefs.h"' lines.  Thanks Roumen Petrov.

Fix configure bug that was misreporting availability of MacOS X 10.5 SDK as available on Linux but not on OS X.

RETSIGTYPE is always void (issue #8510).
pyconfig.h: Regenerate

only whitespace changes in generated configure (diff -uEwB).

Only override the AC_PROG_CC determined CFLAGS if they were set by the user.
This restores the default behavior in the common case of not having CFLAGS
defined when running configure.

framework install of Python in your home directory (on OSX):

   $ configure --enable-framework=${HOME}/Library/Frameworks
   $ make && make install

Without this patch the framework would get installed just fine,
but 'make install' would try to install the application bundles
and command-line tools outside the user's home, which doesn't work
for non-admin users (and is bad form anyway).

to CFLAGS instead of BASECFLAGS.

This fixes issue 8366 and is needed due to
changes introduced in the fix for issue 1628484.

1) A non-critical off-by-one error in pythonw

2) A problem in the configure script that caused
   builds with '--enable-framework --enable-universalsdk=/'
   to fail on OSX 10.6.

optimizations are disabled when --with-pydebug is used.

build (all other definition where correct).

and that it doesn't default to the 10.4u SDK when that SDK does not exist.

(This affects OSX)

This patch should fix most of issue 4834, although I haven't gotten enough
information from the user to be sure.

- Issue #7714: Use ``gcc -dumpversion`` to detect the version of GCC on
  MacOSX.

- Make configure look for util.h as well as libutil.h. The former
  is the header file that on OSX contains the defition of openpty.

  (Needed to compile for OSX 10.4 on OSX 10.6)

- Use the correct definition of CC to compile the pythonw executable

More configure fixes: avoid sh 'integer argument expected' error when 'long long' type doesn't exist.

The previous implementation used execv(2) to run the real interpreter, which means that
you cannot use the arch(1) tool to select the architecture you want to use for a
universal build because that only affects the python/pythonw wrapper and not the actual
interpreter.

The new version uses posix_spawnv with a number of OSX-specific options that ensure that
the real interpreter is started using the same CPU architecture as the wrapper, and that
means that 'arch -ppc python' now actually works.

I've also changed the way that the wrapper looks for the framework: it is now linked to
the framework rather than hardcoding the framework path. This should make it easier to
provide pythonw support in tools like virtualenv.

sem_unlink calls to delete those semaphore files.

Patch from James Henstridge.

access to the initgroups(3) C library call on Unix systems which implement
it.  Patch by Jean-Paul Calderone.

to indicate that semaphores aren't available;  define a new variable
POSIX_SEMAPHORES_NOT_ENABLED instead.

properly, and use this to skip test_multiprocessing on platforms
where sem_open raises a signal.  This should fix some FreeBSD buildbot
failures for test_multiprocessing.