By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,341 Members | 1,681 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,341 IT Pros & Developers. It's quick & easy.

building extension modules under 2.4 / cygwin

P: n/a

For the first time, I am trying to compile a matplotlib installer for
win32 / python2.4 under cygwin. I tested this earlier with one of the
pre-release candidates and had no troubles. But when I compile with
python2.4, I get the following error when I try and import my
extension code

the procedure entry point _ctype could not be located in the dynamic
link libary msvcr71.dll

This DLL resides in C:\Windows\System32 on my system

If I edit the distutils/cygwincompiler.py file and remove the line
that add this lib
elif msc_ver == '1310':
# MSVC 7.1
#self.dll_libraries = ['msvcr71']
self.dll_libraries = []

My code compiles, links and runs fine, at least in initial tests

Any reason I shouldn't be doing this?

JDH

Jul 18 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
John Hunter wrote:
the procedure entry point _ctype could not be located in the dynamic
link libary msvcr71.dll


This sounds like a bug in the Cygwin linker or header files to me.
I cannot fully check, but it seems to me that msvcr71.dll does not
have a _ctype variable. Instead, the is* functions (which may have
traditionally used _ctype - can't check that, either) are now
implemented through function calls. Can you (e.g. using nm) find
out where the reference to _ctype originates from?

If you remove usage of _ctype in your extension module (e.g. by not
using isupper() and the like), it probably will work fine.

Regards,
Martin
Jul 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.