[Grok-dev] Building grok on windows with Python 2.6?

Alec Munro alecmunro at gmail.com
Fri Jan 23 12:50:10 EST 2009


Running it a few times caused it to move on to a new error:

Invoking zc.buildout...
Develop: 'C:\\Temp\\Sample\\.'
Installing eggbasket.
Getting distribution for 'zope.app.securitypolicy==3.4.6'.
eggbasket: Distributions are not installed. A tarball will be downloaded.
eggbasket: Distributions are not installed. A tarball will be downloaded.
eggbasket: Downloading http://grok.zope.org/releaseinfo/grok-eggs-1.0a1.tgz ...
eggbasket: Downloading http://grok.zope.org/releaseinfo/grok-eggs-1.0a1.tgz ...
eggbasket: Finished downloading.
eggbasket: Finished downloading.
eggbasket: Extracting tarball contents...
eggbasket: Extracting tarball contents...
eggbasket: No correct tarball found at http://grok.zope.org/releaseinfo/grok-egg
s-1.0a1.tgz.
eggbasket: No correct tarball found at http://grok.zope.org/releaseinfo/grok-egg
s-1.0a1.tgz.
eggbasket: The error was: bad checksum
eggbasket: The error was: bad checksum

Any idea why I'm getting the duplicate printout?

Thanks,
Alec

On Fri, Jan 23, 2009 at 1:37 PM, Alec Munro <alecmunro at gmail.com> wrote:
> Does this work for anyone?
>
> I can easy_install grokproject, but "grokproject Sample", after
> "Getting distribution for 'grok==1.0a1'." I get:
>
> IOError: [Errno 2] No such file or directory: 'C:\\Documents'
>
> And trying to "easy_install grok", has a problem with zope.security
> (I've got mingw set as the compiler):
>
> Running zope.security-3.5.2\setup.py -q bdist_egg --dist-dir c:\docume~1\amunro\
> locals~1\temp\easy_install-yzoey3\zope.security-3.5.2\egg-dist-tmp-tki_n8
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0x3d): u
> ndefined reference to `_imp__PyCObject_Type'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0x330):
> undefined reference to `_imp___Py_NotImplementedStruct'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0x337):
> undefined reference to `_imp___Py_NotImplementedStruct'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0x453):
> undefined reference to `_imp___Py_NoneStruct'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0x465):
> undefined reference to `_imp__PyExc_ValueError'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0x596):
> undefined reference to `_imp___Py_TrueStruct'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0x59e):
> undefined reference to `_imp___Py_ZeroStruct'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0xaff):
> undefined reference to `_imp__PyExc_TypeError'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0xb3f):
> undefined reference to `_imp__PyExc_TypeError'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0xb7f):
> undefined reference to `_imp__PyExc_TypeError'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0xbbf):
> undefined reference to `_imp__PyExc_TypeError'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0xbff):
> undefined reference to `_imp__PyExc_TypeError'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0xc24):
> undefined reference to `_imp___Py_NoneStruct'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0xff8):
> undefined reference to `_imp___Py_NotImplementedStruct'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0xfff):
> undefined reference to `_imp___Py_NotImplementedStruct'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0x1ad5):
>  undefined reference to `_imp__PyExc_TypeError'
> build\temp.win32-2.6\Release\src\zope\security\_proxy.o:_proxy.c:(.text+0x22c8):
>  undefined reference to `_imp__PyType_Type'
> collect2: ld returned 1 exit status
> error: Setup script exited with error: command 'gcc' failed with exit status 1
>
>
> Any tips?
>
> Thanks,
> Alec
>


More information about the Grok-dev mailing list