Re: [Zope-dev] SVN: persistent/trunk/ Prep 4.0.4 release.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/12/2012 04:12 PM, Roger wrote:
I guess the peristent release is broken. At least with my windows minsys setup. (I don't use cygwin)
Should this work or does persistent require a special build setup?
bin\buildout.exe Develop: 'D:\\svnRefline\\packages\\branches\\dev-2.0-core\\externals\\p01.cdn\\.'
Installing test.
Getting distribution for 'persistent>=4.0.0dev,<4.1dev'. cc1.exe: error: unrecognized command line option '-mno-cygwin' error: Setup script exited with error: command 'gcc' failed with exit status 1 An error occurred when trying to install persistent 4.0.4. Look above this message for any errors that were output by easy_install. While: Installing test. Getting distribution for 'persistent>=4.0.0dev,<4.1dev'. Error: Couldn't install: persistent 4.0.4
I don't know what the error message is about '-mno-cygwin'. I do know that the 4.0.4 release has extension modules which compoile under Python3, but which are not importable: I've been working on that today. Because I'm working on cross-version stuff, I haven't been using zc.buildout. I can install 'persistent==4.0.4' in a virtualenv, howeer, and the buildout works for me under Python 2.x. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDJE34ACgkQ+gerLs4ltQ6fCACgl8w9sn+sJmHIRLn2o0OaHZG3 X3EAoJLDDdJK/ol/UV9Iv5IQaXZXS7K5 =QL7V -----END PGP SIGNATURE-----
On Dec 13, 2012, at 0:30 , Tres Seaver <tseaver@palladion.com> wrote:
Getting distribution for 'persistent>=4.0.0dev,<4.1dev'. cc1.exe: error: unrecognized command line option '-mno-cygwin' error: Setup script exited with error: command 'gcc' failed with exit status 1 An error occurred when trying to install persistent 4.0.4. Look above this message for any errors that were output by easy_install. While: Installing test. Getting distribution for 'persistent>=4.0.0dev,<4.1dev'. Error: Couldn't install: persistent 4.0.4
I don't know what the error message is about '-mno-cygwin'.
From another project where I was forced to use Windoze I dimly remember that this issue arises when compiling any C extension with the installed Python. That "-mno-cygwin" flag is defined deep inside setuptools itself and clashes with newer versions of the compilation tools which don't know that flag anymore. I may have some of the details wrong, but this is *not* an issue with the persistent package requiring a special build setup. The issue is at the Python level and how setuptools interacts with the compiler when building C extensions. In that project I was successfully building extensions using Cygwin. jens
On 12/13/2012 12:30 AM, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/12/2012 04:12 PM, Roger wrote:
I guess the peristent release is broken. At least with my windows minsys setup. (I don't use cygwin)
Should this work or does persistent require a special build setup?
bin\buildout.exe Develop: 'D:\\svnRefline\\packages\\branches\\dev-2.0-core\\externals\\p01.cdn\\.'
Installing test.
Getting distribution for 'persistent>=4.0.0dev,<4.1dev'. cc1.exe: error: unrecognized command line option '-mno-cygwin' error: Setup script exited with error: command 'gcc' failed with exit status 1 An error occurred when trying to install persistent 4.0.4. Look above this message for any errors that were output by easy_install. While: Installing test. Getting distribution for 'persistent>=4.0.0dev,<4.1dev'. Error: Couldn't install: persistent 4.0.4
I don't know what the error message is about '-mno-cygwin'. I do know that the 4.0.4 release has extension modules which compoile under Python3, but which are not importable: I've been working on that today.
Because I'm working on cross-version stuff, I haven't been using zc.buildout. I can install 'persistent==4.0.4' in a virtualenv, howeer, and the buildout works for me under Python 2.x.
Let's put the blame on windows. A process got stuck on winbot, so it could not release the binaries. Now I kicked it and all should be fine. -- Best regards, Adam GROSZER -- Quote of the day: Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity. - General George S. Patton, Jr.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/13/2012 04:45 AM, Adam GROSZER wrote:
Let's put the blame on windows. A process got stuck on winbot, so it could not release the binaries. Now I kicked it and all should be fine.
Was the wedged process also blocking test runners? I haven't seen winbot reports in the daily summary since Sunday. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlDJ8RUACgkQ+gerLs4ltQ70WQCgysEgirM74GgY6hbeuKPy6o3G /b4AoJm0IhYcsvBDoqzpJqnd+6wvSnRs =quLt -----END PGP SIGNATURE-----
On 12/13/2012 04:15 PM, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 12/13/2012 04:45 AM, Adam GROSZER wrote:
Let's put the blame on windows. A process got stuck on winbot, so it could not release the binaries. Now I kicked it and all should be fine.
Was the wedged process also blocking test runners? I haven't seen winbot reports in the daily summary since Sunday.
Yes, it was blocking *all* builders. Also expect a load of errors. -- Best regards, Adam GROSZER -- Quote of the day: Guilt and self-laceration are indulgences
On Thu, Dec 13, 2012 at 05:10:09PM +0100, Adam GROSZER wrote:
On 12/13/2012 04:15 PM, Tres Seaver wrote:
On 12/13/2012 04:45 AM, Adam GROSZER wrote:
Let's put the blame on windows. A process got stuck on winbot, so it could not release the binaries. Now I kicked it and all should be fine.
Was the wedged process also blocking test runners? I haven't seen winbot reports in the daily summary since Sunday.
Yes, it was blocking *all* builders. Also expect a load of errors.
Oh, is that why the test summaries were all "OK" lately? And here I was all happy about the new state of the world. Marius Gedminas -- http://pov.lt/ -- Zope 3/BlueBream consulting and development
participants (4)
-
Adam GROSZER -
Jens Vagelpohl -
Marius Gedminas -
Tres Seaver