From 24cf7766bca616cd5d32e0c707dbcda8941d0a27 Mon Sep 17 00:00:00 2001 From: Jason Tishler Date: Wed, 22 May 2002 16:46:15 +0000 Subject: [PATCH] Patch #491107: Cygwin setup.py import workaround patch mwh wrote: > Jason, feel free to complain if you think this isn't > the right thing to do. I guess that I would like to complain and reopen this issue. :,) I cannot build a Python 2.2.1 with threads under Cygwin without this patch even though I'm using Michael's static _socket workaround. This is due to the Cygwin fork() problem with DLL base address conflicts that are triggered by importing many modules during the setup.py run. Similar problems can also be caused by regrtest.py. Even after my rebase patch is accepted into Cygwin's setup.exe, I feel this patch will still be necessary. This is because during the build process, the shared extensions (i.e., DLLs) will not be rebased yet. Hence, the potential for DLL base address conflicts will exist. One way to obviate this patch is to push the rebase functionality into Cygwin's ld. Unfortunately, I don't think this is likely to happen. Another possible way, is to use the yet to be defined and implemented unload module functionality: http://mail.python.org/pipermail/python-dev/2001-December/019028.html --- setup.py | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/setup.py b/setup.py index d5579435460..d2b3947856a 100644 --- a/setup.py +++ b/setup.py @@ -168,6 +168,12 @@ def build_extension(self, ext): 'WARNING: skipping import check for Carbon-based "%s"' % ext.name) return + # Workaround for Cygwin: Cygwin currently has fork issues when many + # modules have been imported + if self.get_platform() == 'cygwin': + self.announce('WARNING: skipping import check for Cygwin-based "%s"' + % ext.name) + return ext_filename = os.path.join( self.build_lib, self.get_ext_filename(self.get_ext_fullname(ext.name)))