Disabled -prebind again when linking the interpreter on MacOSX. It ca…

…used

a serious slowdown when loading dynamic modules that depend on large shared
libraries or frameworks.

configure

@@ -9443,11 +9443,10 @@ then
 		# -u _PyMac_Error is needed to pull in the mac toolbox glue, which is
 		# not used by the core itself but which needs to be in the core so
 		# that dynamically loaded extension modules have access to it.
-		# -prebind causes the executable to assume dynamic libraries are at their
-		# preferred address, which speeds up startup. We specify it here
-		# in stead of in LDFLAGS because it does not seem to work for bundle
-		# plugins (as of OSX 10.2).
-		LINKFORSHARED="$extra_undefs -framework System -prebind"
+		# -prebind is no longer used, because it actually seems to give a
+		# slowdown in stead of a speedup, maybe due to the large number of
+		# dynamic loads Python does.
+		LINKFORSHARED="$extra_undefs -framework System"
 		if test "$enable_framework"
 		then
 			LINKFORSHARED="$LINKFORSHARED -framework Python"

configure.in

@@ -1164,11 +1164,10 @@ then
 		# -u _PyMac_Error is needed to pull in the mac toolbox glue, which is
 		# not used by the core itself but which needs to be in the core so
 		# that dynamically loaded extension modules have access to it.
-		# -prebind causes the executable to assume dynamic libraries are at their
-		# preferred address, which speeds up startup. We specify it here
-		# in stead of in LDFLAGS because it does not seem to work for bundle
-		# plugins (as of OSX 10.2).
-		LINKFORSHARED="$extra_undefs -framework System -prebind"
+		# -prebind is no longer used, because it actually seems to give a
+		# slowdown in stead of a speedup, maybe due to the large number of
+		# dynamic loads Python does.
+		LINKFORSHARED="$extra_undefs -framework System"
 		if test "$enable_framework"
 		then
 			LINKFORSHARED="$LINKFORSHARED -framework Python"