>>>>> "Jason" == Jason Tishler <[EMAIL PROTECTED]> writes:
Jason> Volker, Jason> On Sun, Mar 09, 2003 at 03:15:55PM +0100, Dr. Volker Zell wrote: >> Yes there is one on SF. Jason> I just tried Numeric-23.0 -- still works for me. >> Do you know where the -L stuff is generated Jason> IIRC, distutils "greps" this out of /usr/lib/python2.2/config/Makefile. Jason> However, I haven't been in this "special place" since I added shared Jason> extension support to Cygwin Python -- about 2 years. >> or how I can debug this further ? Jason> Sorry, until others have this problem, you will have to debug this Jason> yourself. OK I found it. >From /lib/python2.2/distutils/command/build_ext.py: # for extensions under Cygwin Python's library directory must be # appended to library_dirs if sys.platform[:6] == 'cygwin': if string.find(sys.executable, sys.exec_prefix) != -1: # building third party extensions self.library_dirs.append(os.path.join(sys.prefix, "lib", "python" + sys.version[:3], "config")) else: # building python standard extensions self.library_dirs.append('.') I always invoked /bin/python setup.py build because I had an old selfcompiled version of python in /usr/local/bin and so string.find gives -1 because sys.exec_prefix seems to be /usr So when I invoke it with /usr/bin/python everything's okay. If somebody has /bin in front of /usr/bin in his or her PATH, third party extensions will fail to build properly when just calling python setup.py build. Jason> Jason Ciao Volker -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/