Re: [gentoo-user] Compilation aborted for setuptools-0.6.12
On 6/19/10, meino.cra...@gmx.de meino.cra...@gmx.de wrote: Hi, compilation of setuptools-0.6.12 aborts woth: copying tests/api_tests.txt - build/src/tests Traceback (most recent call last): File setup.py, line 24, in module from lib2to3.main import main File /usr/lib/python3.1/lib2to3/main.py, line 12, in module from . import refactor File /usr/lib/python3.1/lib2to3/refactor.py, line 25, in module from . import pytree, pygram File /usr/lib/python3.1/lib2to3/pygram.py, line 35, in module del python_grammar_no_print_statement.keywords[print] KeyError: 'print' Over here it seems to run a piece printing out messages starting with RefactoringTool: where it fails for you. AFAICT, 2to3-refactoring stuff is part of dev-lang/python package itself. So, I wonder if emerge -1 python:2.6 would help? (Or grabbing a pre-compiled binary from tinderbox.dev.gentoo.org if the emerge fails.) -- Arttu V.
Re: [gentoo-user] Compilation aborted for setuptools-0.6.12
Arttu V. arttu...@gmail.com [10-06-20 12:28]: On 6/19/10, meino.cra...@gmx.de meino.cra...@gmx.de wrote: Hi, compilation of setuptools-0.6.12 aborts woth: copying tests/api_tests.txt - build/src/tests Traceback (most recent call last): File setup.py, line 24, in module from lib2to3.main import main File /usr/lib/python3.1/lib2to3/main.py, line 12, in module from . import refactor File /usr/lib/python3.1/lib2to3/refactor.py, line 25, in module from . import pytree, pygram File /usr/lib/python3.1/lib2to3/pygram.py, line 35, in module del python_grammar_no_print_statement.keywords[print] KeyError: 'print' Over here it seems to run a piece printing out messages starting with RefactoringTool: where it fails for you. AFAICT, 2to3-refactoring stuff is part of dev-lang/python package itself. So, I wonder if emerge -1 python:2.6 would help? (Or grabbing a pre-compiled binary from tinderbox.dev.gentoo.org if the emerge fails.) -- Arttu V. Hi Arttu, thanks for your posting! :) Python2.6 compiles fine, setuptool fails again at the same point... What can I try next? Have a nice weekend! Best regards, mcc
Re: [gentoo-user] Compilation aborted for setuptools-0.6.12
On 6/20/10, meino.cra...@gmx.de meino.cra...@gmx.de wrote: Arttu V. arttu...@gmail.com [10-06-20 12:28]: On 6/19/10, meino.cra...@gmx.de meino.cra...@gmx.de wrote: Hi, compilation of setuptools-0.6.12 aborts woth: copying tests/api_tests.txt - build/src/tests Traceback (most recent call last): File setup.py, line 24, in module from lib2to3.main import main File /usr/lib/python3.1/lib2to3/main.py, line 12, in module from . import refactor File /usr/lib/python3.1/lib2to3/refactor.py, line 25, in module from . import pytree, pygram File /usr/lib/python3.1/lib2to3/pygram.py, line 35, in module del python_grammar_no_print_statement.keywords[print] KeyError: 'print' Over here it seems to run a piece printing out messages starting with RefactoringTool: where it fails for you. AFAICT, 2to3-refactoring stuff is part of dev-lang/python package itself. So, I wonder if emerge -1 python:2.6 would help? (Or grabbing a pre-compiled binary from tinderbox.dev.gentoo.org if the emerge fails.) -- Arttu V. Hi Arttu, thanks for your posting! :) Python2.6 compiles fine, setuptool fails again at the same point... What can I try next? Short of recompiling also python 3.1 (with distcc, ccache and such possible interference disabled) -- I'm out out ideas. -- Arttu V.
Re: [gentoo-user] Compilation aborted for setuptools-0.6.12
Arttu V. arttu...@gmail.com [10-06-20 14:04]: On 6/20/10, meino.cra...@gmx.de meino.cra...@gmx.de wrote: Arttu V. arttu...@gmail.com [10-06-20 12:28]: On 6/19/10, meino.cra...@gmx.de meino.cra...@gmx.de wrote: Hi, compilation of setuptools-0.6.12 aborts woth: copying tests/api_tests.txt - build/src/tests Traceback (most recent call last): File setup.py, line 24, in module from lib2to3.main import main File /usr/lib/python3.1/lib2to3/main.py, line 12, in module from . import refactor File /usr/lib/python3.1/lib2to3/refactor.py, line 25, in module from . import pytree, pygram File /usr/lib/python3.1/lib2to3/pygram.py, line 35, in module del python_grammar_no_print_statement.keywords[print] KeyError: 'print' Over here it seems to run a piece printing out messages starting with RefactoringTool: where it fails for you. AFAICT, 2to3-refactoring stuff is part of dev-lang/python package itself. So, I wonder if emerge -1 python:2.6 would help? (Or grabbing a pre-compiled binary from tinderbox.dev.gentoo.org if the emerge fails.) -- Arttu V. Hi Arttu, thanks for your posting! :) Python2.6 compiles fine, setuptool fails again at the same point... What can I try next? Short of recompiling also python 3.1 (with distcc, ccache and such possible interference disabled) -- I'm out out ideas. -- Arttu V. Hi Arttu, thanks again for your help ! :) Tried that...python3.1 compiles fine, setuptools failed. And now? Best regards, mcc
Re: [gentoo-user] Compilation aborted for setuptools-0.6.12
meino.cra...@gmx.de writes: Tried that...python3.1 compiles fine, setuptools failed. And now? How about putting dev-python/setuptools into /etc/portage/package.keywords, and trying to emerge 0.6.13? Wonko
Re: [gentoo-user] Compilation aborted for setuptools-0.6.12
Alex Schuster wo...@wonkology.org [10-06-20 15:16]: meino.cra...@gmx.de writes: Tried that...python3.1 compiles fine, setuptools failed. And now? How about putting dev-python/setuptools into /etc/portage/package.keywords, and trying to emerge 0.6.13? Wonko Hi, thanks for your posting, Wonko! :) Is there any Changelog-issue in that version, that says anything related to the compilation problem? I tried to re-emerge setuptools 0.6.10 and it fails the same way. So I believe (=not knowing) that this problem is caused by something outside setuptools, which gets screwed up. Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10 (current version) is gone and cannot get back due to the same problem (see above). And then I have a unstable version, which may pull in other unstable versions of something else, which pull in This way I have corrupted my last installed gentoo system... Best regards, mcc
Re: [gentoo-user] Compilation aborted for setuptools-0.6.12
meino.cra...@gmx.de writes: Alex Schuster wo...@wonkology.org [10-06-20 15:16]: How about putting dev-python/setuptools into /etc/portage/package.keywords, and trying to emerge 0.6.13? I tried to re-emerge setuptools 0.6.10 and it fails the same way. So I believe (=not knowing) that this problem is caused by something outside setuptools, which gets screwed up. Probably python itself, as Arttu pointed out. Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10 (current version) is gone and cannot get back due to the same problem (see above). And then I have a unstable version, which may pull in other unstable versions of something else, which pull in Maybe, but at least in the ebuild itself there are no such dependencies. If you'd need to keyword this package only, it should do no harm. If more things need to be keyworded, I agree that this tends to make things complicated. But at least you can quickpkg the existing version, and get it back when needed without compiling with emerge -k. But when 0.6.10 also fails, the problem is likely to be somewhere else. This way I have corrupted my last installed gentoo system... I'm at ~amd64 now, and things are easier now :) At least for me. If you are desperate: Maybe removing setuptools would at least make python-updater run through, unless something would pull it in again. Emerge -k setuptools back. You may be missing stuff for python 3.1, but maybe this does not harm too much. And report a bug at bugs.gentoo.org, so the maintainers know what's going on. Wonko
Re: [gentoo-user] Compilation aborted for setuptools-0.6.12
Alex Schuster wo...@wonkology.org [10-06-20 17:08]: meino.cra...@gmx.de writes: Alex Schuster wo...@wonkology.org [10-06-20 15:16]: How about putting dev-python/setuptools into /etc/portage/package.keywords, and trying to emerge 0.6.13? I tried to re-emerge setuptools 0.6.10 and it fails the same way. So I believe (=not knowing) that this problem is caused by something outside setuptools, which gets screwed up. Probably python itself, as Arttu pointed out. Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10 (current version) is gone and cannot get back due to the same problem (see above). And then I have a unstable version, which may pull in other unstable versions of something else, which pull in Maybe, but at least in the ebuild itself there are no such dependencies. If you'd need to keyword this package only, it should do no harm. If more things need to be keyworded, I agree that this tends to make things complicated. But at least you can quickpkg the existing version, and get it back when needed without compiling with emerge -k. But when 0.6.10 also fails, the problem is likely to be somewhere else. This way I have corrupted my last installed gentoo system... I'm at ~amd64 now, and things are easier now :) At least for me. If you are desperate: Maybe removing setuptools would at least make python-updater run through, unless something would pull it in again. Emerge -k setuptools back. You may be missing stuff for python 3.1, but maybe this does not harm too much. And report a bug at bugs.gentoo.org, so the maintainers know what's going on. Wonko Hi Wonko, I checked the dependencies. Python-updater would recompile gnumeric,boost and setuptools. setuptools will be pulled in last consequence from inkscape and gnumeric (not directly). Best regards, mcc
Re: [gentoo-user] Compilation aborted for setuptools-0.6.12
On Sunday 20 June 2010 16:05:58 Alex Schuster wrote: meino.cra...@gmx.de writes: Alex Schuster wo...@wonkology.org [10-06-20 15:16]: How about putting dev-python/setuptools into /etc/portage/package.keywords, and trying to emerge 0.6.13? I tried to re-emerge setuptools 0.6.10 and it fails the same way. So I believe (=not knowing) that this problem is caused by something outside setuptools, which gets screwed up. Probably python itself, as Arttu pointed out. Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10 (current version) is gone and cannot get back due to the same problem (see above). And then I have a unstable version, which may pull in other unstable versions of something else, which pull in Maybe, but at least in the ebuild itself there are no such dependencies. If you'd need to keyword this package only, it should do no harm. If more things need to be keyworded, I agree that this tends to make things complicated. But at least you can quickpkg the existing version, and get it back when needed without compiling with emerge -k. But when 0.6.10 also fails, the problem is likely to be somewhere else. This way I have corrupted my last installed gentoo system... I'm at ~amd64 now, and things are easier now :) At least for me. If you are desperate: Maybe removing setuptools would at least make python-updater run through, unless something would pull it in again. Emerge -k setuptools back. You may be missing stuff for python 3.1, but maybe this does not harm too much. And report a bug at bugs.gentoo.org, so the maintainers know what's going on. I'd have another go but after setting MAKEOPTS=-j1 (although I have to admit the error you posted does not look like this would make any difference). -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Compilation aborted for setuptools-0.6.12
Mick michaelkintz...@gmail.com [10-06-20 18:38]: On Sunday 20 June 2010 16:05:58 Alex Schuster wrote: meino.cra...@gmx.de writes: Alex Schuster wo...@wonkology.org [10-06-20 15:16]: How about putting dev-python/setuptools into /etc/portage/package.keywords, and trying to emerge 0.6.13? I tried to re-emerge setuptools 0.6.10 and it fails the same way. So I believe (=not knowing) that this problem is caused by something outside setuptools, which gets screwed up. Probably python itself, as Arttu pointed out. Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10 (current version) is gone and cannot get back due to the same problem (see above). And then I have a unstable version, which may pull in other unstable versions of something else, which pull in Maybe, but at least in the ebuild itself there are no such dependencies. If you'd need to keyword this package only, it should do no harm. If more things need to be keyworded, I agree that this tends to make things complicated. But at least you can quickpkg the existing version, and get it back when needed without compiling with emerge -k. But when 0.6.10 also fails, the problem is likely to be somewhere else. This way I have corrupted my last installed gentoo system... I'm at ~amd64 now, and things are easier now :) At least for me. If you are desperate: Maybe removing setuptools would at least make python-updater run through, unless something would pull it in again. Emerge -k setuptools back. You may be missing stuff for python 3.1, but maybe this does not harm too much. And report a bug at bugs.gentoo.org, so the maintainers know what's going on. I'd have another go but after setting MAKEOPTS=-j1 (although I have to admit the error you posted does not look like this would make any difference). -- Regards, Mick Hi Mick, thanks for your posting! I set it to -j 1 and setuptools fails as before... Best regards, mcc
[gentoo-user] Compilation aborted for setuptools-0.6.12
Hi,
compilation of setuptools-0.6.12 aborts woth:
copying tests/api_tests.txt - build/src/tests
Traceback (most recent call last):
File setup.py, line 24, in module
from lib2to3.main import main
File /usr/lib/python3.1/lib2to3/main.py, line 12, in module
from . import refactor
File /usr/lib/python3.1/lib2to3/refactor.py, line 25, in module
from . import pytree, pygram
File /usr/lib/python3.1/lib2to3/pygram.py, line 35, in module
del python_grammar_no_print_statement.keywords[print]
KeyError: 'print'
* ERROR: dev-python/setuptools-0.6.12 failed:
* Building failed with CPython 3.1 in distutils_building() function
*
* Call stack:
* ebuild.sh, line 54: Called src_compile
* environment, line 4648: Called distutils_src_compile
* environment, line 1278: Called python_execute_function
'distutils_building'
* environment, line 3426: Called die
* The specific snippet of code:
* die ${failure_message};
*
* If you need support, post the output of 'emerge --info
=dev-python/setuptools-0.6.12',
* the complete build log and the output of 'emerge -pqv
=dev-python/setuptools-0.6.12'.
* The complete build log is located at
'/var/tmp/portage/dev-python/setuptools-0.6.12/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/dev-python/setuptools-0.6.12/temp/environment'.
* S: '/var/tmp/portage/dev-python/setuptools-0.6.12/work/distribute-0.6.12'
Failed to emerge dev-python/setuptools-0.6.12, Log file:
'/var/tmp/portage/dev-python/setuptools-0.6.12/temp/build.log'
* Messages for package dev-python/setuptools-0.6.12:
* ERROR: dev-python/setuptools-0.6.12 failed:
* Building failed with CPython 3.1 in distutils_building() function
*
* Call stack:
* ebuild.sh, line 54: Called src_compile
* environment, line 4648: Called distutils_src_compile
* environment, line 1278: Called python_execute_function
'distutils_building'
* environment, line 3426: Called die
* The specific snippet of code:
* die ${failure_message};
*
* If you need support, post the output of 'emerge --info
=dev-python/setuptools-0.6.12',
* the complete build log and the output of 'emerge -pqv
=dev-python/setuptools-0.6.12'.
* The complete build log is located at
'/var/tmp/portage/dev-python/setuptools-0.6.12/temp/build.log'.
* The ebuild environment file is located at
'/var/tmp/portage/dev-python/setuptools-0.6.12/temp/environment'.
* S: '/var/tmp/portage/dev-python/setuptools-0.6.12/work/distribute-0.6.12'
solfire:/rootqsearch setuptools
search: Updating ebuild cache ...
search: Finished 27398 entries in 0.474906 seconds
dev-python/setuptools Distribute (fork of Setuptools) is a collection of
extensions to Distutils
f you need the addtional files mentioned above please dont hesitat to
mail me.
I only dont with to clutter the mailing list.
How can I fix that bug?
Best regards.
mcc
