Godefroid Chapelle wrote:

Hi,

When running the Zope3 C extensions building script, I get the following message generated by distutils.spawn module :

Building extensions in C:\Projects\Zope3\lib\python\Zope\Security running build_ext building '_Proxy' extension skipping _Proxy.c (build\temp.win32-2.2\Release\_proxy.obj up-to-date) writing build\temp.win32-2.2\Release\_Proxy.def c:\Program Files\Borland\Bcc55\bin\ilink32.exe /Tpd /Gn /q /x /LC:\Python22\libs /L. "/Lc:\Program Files\Borland\Bcc55\lib" c0d32 build\temp.win32-2.2\Release\_ proxy.obj , _Proxy.pyd ,, C:\Python22\libs\python22_bcpp.lib import32 cw32mt , b uild\temp.win32-2.2\Release\_Proxy.def , Fatal: Unable to open file 'LIB.OBJ' error: command 'ilink32.exe' failed with exit status 2

I have not been able to find out where this LIB.OBJ file should be found. I wonder if it comes from the Borland side or from the Python library side.

I think this is a problem with the quoting in the command line. "/Lc:\Program Files\Borland\Bcc55\lib" probably is interpreted as /Lc:\Program Files\Borland\Bcc55\lib You could try to fix the command line quoting in distutils (file bcppcompiler.py in method link. I would do, but I don't have a Windows machine available now.) or you install bcc55 in a path with spaces in it.

I must say that the _proxy.obj was built on my machine with the compiler.

Any help appreciated. --

Godefroid Chapelle

Kind regards Rene Liebscher