Removed NeXT notes (replacing them with a line saying NeXT is no

longer supported) and updated MacOSX notes.

README

@@ -300,8 +300,8 @@ SunOS 4.x: When using the SunPro C compiler, you may want to use the
 	'-Xa' option instead of '-Xc', to enable some needed non-ANSI
 	Sunisms.
 
-NeXT:   To build fat binaries, use the --with-next-archs switch
-	described below.
+NeXT:   Not supported anymore. Start with the MacOSX/Darwin code if you
+	want to revive it.
 
 QNX:	Chris Herborth (chrish@qnx.com) writes:
 	configure works best if you use GNU bash; a port is available on
@@ -386,16 +386,22 @@ Reliant UNIX: The thread support does not compile on Reliant UNIX, and
         platform as well.  This should be resolved in time for a
         future release.
 
-Mac OS X 10.0: Run configure with "OPT='-no-cpp-precomp' ./configure
-        --with-suffix=.exe --with-dyld".  This generates executable
-        file: 'python.exe' (it cannot be named 'python' on an HFS or
-        HFS+ disk as the file name clashes with directory 'Python').
-        The '-no-cpp-precomp' option prevents a large number of
-        compilation warnings.  One of the regular expression tests
-        fails with a SEGV due to the small stack size used by default
-        (how to change this?), and the test_largefile test is only
-        expected to work on a Unix UFS filesystem (how to check for
-        this on Mac OS X?).
+Mac OS X 10.0: Run configure with "./configure --with-suffix=.exe".
+        This generates executable file: 'python.exe' (it cannot be named
+        'python' on an HFS or HFS+ disk as the file name clashes with
+        directory 'Python'). One of the regular expression tests fails
+        with a SEGV due to the small stack size used by default (how to
+        change this?), and the test_largefile test is only expected to
+        work on a Unix UFS filesystem (how to check for this on Mac OS
+        X?).
+        On naked Darwin you may have to add the configure option
+        "--without-toolbox-glue" to disable the glue code for the Carbon
+        interface modules. (The modules themselves are currently not built
+        by default as they are experimental, on real OSX you can enable them
+        in setup.py).
+        You may want to try the configure option "--enable-framework" which
+        installs Python as a framework. The location can be set as argument
+        to the --enable-framework option (default /Library/Frameworks).
 
 Cygwin: Cygwin Python builds OOTB when configured as follows:
 
@@ -618,6 +624,11 @@ Emacs found in Misc/python-mode.el.  (But then again, more recent
 versions of Emacs may already have it.)  Follow the instructions that
 came with Emacs for installation of site-specific files.
 
+On Mac OS X, if you have configured Python with --enable-framework, you
+should use "make frameworkinstall" to do the installation. Note that this
+installs the Python executable in a place that is not normally on your
+PATH, you may want to set up a symlink in /usr/local/bin.
+
 
 Configuration options and variables
 -----------------------------------
@@ -701,11 +712,6 @@ Modules/getpath.o.
 	--with-libc=-lc_s. These libraries are passed after all other
 	libraries, the C library last.
 
---with-next-archs='arch1 arch2': Under NEXTSTEP, this will build
-	all compiled binaries with the architectures listed.  This will
-	also correctly set the target architecture-specific resource
-	directory.  (This option is not supported on other platforms.)
-
 --with-libs='libs': Add 'libs' to the LIBS that the python interpreter
 	is linked against.