Mailman 3 January 2001 - Distutils-SIG

SWIG+distutils+Windows???
by Michel Van den Bergh Jan. 4, 2001

Jan. 4, 2001

Hi I am trying to generate an extension module using distutils on windows. I am using the plain vanilla command python setup.py build_ext -ccygwin (the corresponding command without the -ccygwin works fine on Linux). The source for the extension module was generated by SWIG on Linux (as I don't have SWIG on windows). Compiling seems to go fine but then I get a bunch of undefined symbols: Cannot export init_hintmodule: symbol not defined build\temp.win32-2.0\Release\gtlevel\src\hint_wrap.o(.text+0x165):hint_wrap.c: undefined reference to `_imp__PyExc_NameError' build\temp.win32-2.0\Release\gtlevel\src\hint_wrap.o(.text+0x1f1):hint_wrap.c: undefined reference to `_imp__PyExc_NameError' build\temp.win32-2.0\Release\gtlevel\src\hint_wrap.o(.text+0x230):hint_wrap.c: undefined reference to `_imp__PyType_Type' build\temp.win32-2.0\Release\gtlevel\src\hint_wrap.o(.text+0x9e2):hint_wrap.c: undefined reference to `_imp___Py_NoneStruct' build\temp.win32-2.0\Release\gtlevel\src\hint_wrap.o(.text+0x9e9):hint_wrap.c: undefined reference to `_imp___Py_NoneStruct' build\temp.win32-2.0\Release\gtlevel\src\hint_wrap.o(.text+0xa22):hint_wrap.c: undefined reference to `_imp___Py_NoneStruct' build\temp.win32-2.0\Release\gtlevel\src\hint_wrap.o(.text+0xa29):hint_wrap.c: undefined reference to `_imp___Py_NoneStruct' build\temp.win32-2.0\Release\gtlevel\src\hint_wrap.o(.text+0xa99):hint_wrap.c: undefined reference to `_imp__PyExc_TypeError' build\temp.win32-2.0\Release\gtlevel\src\hint_wrap.o(.text+0xb3d):hint_wrap.c: undefined reference to `_imp__PyExc_TypeError' collect2: ld returned 1 exit status error: command 'gcc' failed with exit status 1 I have no idea what the problem is here. Is there anybody than can help? I suspect this must be trivial for a knowledgeable person. The version numbers are as follows: gcc 2.95.2 ld 2.10.90 dllwrap 2.10.90 Best regards. Michel ====================================== Linux: the choice of a GNU generation.

5 6

Re: [Distutils] Platform specific defaults for config options.
by Michel Van den Bergh Jan. 4, 2001

Jan. 4, 2001

Rene Liebscher wrote: > Michel Van den Bergh wrote: > > > > Hello, > > > > After the extremely useful replies I got to my last question here is > > another one! > > > > Is is possible to set defaults for command line options in setup.py? > > > > I would like to put in some PLATFORM-SPECIFIC defaults. E.g, choice > > of compiler, installation directory. > > > > The limited format of config.cfg does not seem to allow this. > > > You probably have to overwrite the Distribution class. > (you can find it in distutils/dist.py) > > You could set your options right in self.__init__() or so, > see also self.command_options > and self.parse_config_files(). > > See also > http://mail.python.org/pipermail/distutils-sig/1999-January/000143.html > You have write then your setup like this: > ------------------------------------------------------------------------ > from distutils.core import Distribution, setup > > class MyDistribution (Distribution): > def __init__(self): > Distribution.__init__(self) > # put your initialization here > > setup (distclass = MyDistribution) > ------------------------------------------------------------------------ > > BTW, I have never extended the Distribution class, so I can't > guarantee it is correct. > > Kind regards > Rene Liebscher Thanks, Using your idea I could inspect the mechanics of distutils a little better. Then I found out that setup has an option 'options' (undocumented as far as I can tell) which allows you to give default values for options. So it is actually pretty easy. It think it would be better to have config files of the form : setup_osname. This would be more transparent. Regards, Michel

1 0

Platform specific defaults for config options.
by Michel Van den Bergh Jan. 4, 2001

Jan. 4, 2001

Hello, After the extremely useful replies I got to my last question here is another one! Is is possible to set defaults for command line options in setup.py? I would like to put in some PLATFORM-SPECIFIC defaults. E.g, choice of compiler, installation directory. The limited format of config.cfg does not seem to allow this. Thanks, Michel

1 0

installer does not see current Pythons
by Rene Liebscher Jan. 4, 2001

Jan. 4, 2001

Any ideas how to solve this, or needs this for some users a special distribution as zip-file. > Support Request #110549, was updated on 2000-Dec-22 17:22 > You can respond by visiting: > http://sourceforge.net/support/?func=detailsupport&support_id=110549&group_… > > Category: None > Status: Open > Priority: 5 > Summary: installer does not see current Pythons > > By: fredy > Date: 2000-Dec-22 17:22 > > Message: > Logged In: YES > user_id=20580 > Browser: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0) > > I downloaded PyOpenGL-1.5.6b1.win32-py1.5.2.exe and > executed it on my Windows NT 4.0 machine. When the > installer displays the "select python installation to > use" screen it fails to list anything and I am > blocked, even though I have both Python 1.5.2 and 1.6 > installed, along with whatever Python comes with Zope > 2.2. What can I do now to install PyOpenGL? > Kind regards Rene Liebscher

1 1

Re: [Distutils] SWIG+distutils+Windows???
by Michel Van den Bergh Jan. 3, 2001

Jan. 3, 2001

Norman Vine wrote: > > Michel Van den Bergh writes: > >>> > >> Norman > >Thanks for the suggestion, but I am just using the vanilla ActiveState > >Python2.0. > >I tried to add USE_DLL_IMPORT to the gcc flags anyway but it > >didn't make > >any difference. The same symbols remain undefined. I really don't > >understand what goes on here. These symbols are referenced in Python.h > >and descendants as externals but they don't seem to be in python20.lib > >(I checked with nm). > >I also tried SWIG on Windows but that didn't help either (I > >didn't think it would). > > I do not think you will have much luck compiling against a non-cygwin > python with Cygwin unless you are using the --no-cygwin switch > > FWIW > These undefined symbols are coming from PY_SRC / include / object.h > > Python compiles fine as a dll with this patch > http://sourceforge.net/patch/?func=detailpatch&patch_id=102409&group_id=5470 > > I haven't tried to get this working with Distutils > > Also when using the Cygwin compiler and embedding python > I had to add the -DUSE_DLL_IMPORT flag when using a cygwin > compiled python in dll form. I did not need this flag with a static > library. Again this is all using the above patch and a recent Cygwin > > Sorry I can not be of more help > > Norman Thanks anyway! Michel

1 0

Re: [Distutils] SWIG+distutils+Windows???
by Michel Van den Bergh Jan. 3, 2001

Jan. 3, 2001

Norman Vine wrote: > > Michel Van den Bergh writes: > > > > > >Hi I am trying to generate an extension module using distutils on windows. > >I am using the plain vanilla command > > > >python setup.py build_ext -ccygwin > > > >(the corresponding command without the -ccygwin works fine on Linux). > > > >The source for the extension module was generated by SWIG on > >Linux (as I don't have SWIG on windows). > > FWIW SWIG compiles OTB with Cygwin > > Are you building this against a Cygwin compiled python > > if so you probably need to add > -DUSE_DLL_IMPORT to the gcc flags > > Norman Thanks for the suggestion, but I am just using the vanilla ActiveState Python2.0. I tried to add USE_DLL_IMPORT to the gcc flags anyway but it didn't make any difference. The same symbols remain undefined. I really don't understand what goes on here. These symbols are referenced in Python.h and descendants as externals but they don't seem to be in python20.lib (I checked with nm). I also tried SWIG on Windows but that didn't help either (I didn't think it would). Regards, Michel

1 0

Re: [Distutils] SWIG+distutils+Windows???
by Michel Van den Bergh Jan. 3, 2001

Jan. 3, 2001

"John J. Lee" wrote: > > On Tue, 2 Jan 2001, Michel Van den Bergh wrote: > [...] > > Compiling seems to go fine but then I get a bunch of undefined symbols: > [...] > > Do you have a libpython20.so? > > John Hello, I am having problems on Windows (on Linux everything works without a hitch). I do have python20.dll as well as python20.lib (which is the import library I presume). The strange thing is that the symbols that the linker is missing on Windows are also the ones which are undefined in Linux (I checked with nm). So this seems to be normal. Unfortunately under Windows the linker views it as an error. This must have something to do with the peculiar nature of the dll file format. I would really like to solve this problem. I tried to compile manually but I always get the same error. Do you know anybody who is knowledgeable in cygwin? Regards, Michel

1 0