This morning I updated my newly installed Gentoo.
Via "eselect read news" I was told, that a new
python version (3.1.*) was installed and I should
run python-updater, which I did.
while compiling boost, the PC was killed. It looks
like it was told to switch off itsself.
I rebooted the PC into runlevel 2 and repeated the
whole thing. Again compiling/merging boost kills
the PC the same way.
I rebooted the PC into runlevel "S". After starting
python-updater compiling/mergeing boost kills the
PC.
Each time it looks like someone has switched off the
power.
From emerge log:
1275759027: Started emerge on: Jun 05, 2010 19:30:27
1275759027: *** emerge --deep --oneshot --keep-going --verbose app-office/gnumeric:0 dev-libs/boost:1.41 dev-python/lxml:0 dev-python/setuptools:0
1275759031: >>> emerge (1 of 4) dev-python/setuptools-0.6.10 to /
1275759033: === (1 of 4) Cleaning (dev-python/setuptools-0.6.10::/usr/portage/dev-python/setuptools/setuptools-0.6.10.ebuild)
1275759033: === (1 of 4) Compiling/Merging (dev-python/setuptools-0.6.10::/usr/portage/dev-python/setuptools/setuptools-0.6.10.ebuild)
1275759046: >>> emerge (1 of 3) dev-libs/boost-1.41.0-r3 to /
1275759048: === (1 of 3) Cleaning (dev-libs/boost-1.41.0-r3::/usr/portage/dev-libs/boost/boost-1.41.0-r3.ebuild)
1275759048: === (1 of 3) Compiling/Merging (dev-libs/boost-1.41.0-r3::/usr/portage/dev-libs/boost/boost-1.41.0-r3.ebuild)
1275760538: Started emerge on: Jun 05, 2010 19:55:38
1275760538: *** emerge --deep --oneshot --keep-going --verbose app-office/gnumeric:0 dev-libs/boost:1.41 dev-python/lxml:0 dev-python/setuptools:0
1275760552: >>> emerge (1 of 4) dev-python/setuptools-0.6.10 to /
1275760553: === (1 of 4) Cleaning (dev-python/setuptools-0.6.10::/usr/portage/dev-python/setuptools/setuptools-0.6.10.ebuild)
1275760553: === (1 of 4) Compiling/Merging (dev-python/setuptools-0.6.10::/usr/portage/dev-python/setuptools/setuptools-0.6.10.ebuild)
1275760566: >>> emerge (1 of 3) dev-libs/boost-1.41.0-r3 to /
1275760569: === (1 of 3) Cleaning (dev-libs/boost-1.41.0-r3::/usr/portage/dev-libs/boost/boost-1.41.0-r3.ebuild)
1275760569: === (1 of 3) Compiling/Merging (dev-libs/boost-1.41.0-r3::/usr/portage/dev-libs/boost/boost-1.41.0-r3.ebuild)
From summary.log:
>>> Messages generated by process 12966 on 2010-06-05 19:30:43 CEST for package dev-python/setuptools-0.6.10:
ERROR: compile
ERROR: dev-python/setuptools-0.6.10 failed:
Building failed with CPython 3.1 in distutils_building() function
Call stack:
ebuild.sh, line 54: Called src_compile
environment, line 4635: Called distutils_src_compile
environment, line 1255: Called python_execute_function 'distutils_building'
environment, line 3413: 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.10',
the complete build log and the output of 'emerge -pqv =dev-python/setuptools-0.6.10'.
The complete build log is located at '/var/tmp/portage/dev-python/setuptools-0.6.10/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/dev-python/setuptools-0.6.10/temp/environment'.
S: '/var/tmp/portage/dev-python/setuptools-0.6.10/work/distribute-0.6.10'
>>> Messages generated by process 6885 on 2010-06-05 19:56:04 CEST for package dev-python/setuptools-0.6.10:
ERROR: compile
ERROR: dev-python/setuptools-0.6.10 failed:
Building failed with CPython 3.1 in distutils_building() function
Call stack:
ebuild.sh, line 54: Called src_compile
environment, line 4643: Called distutils_src_compile
environment, line 1263: Called python_execute_function 'distutils_building'
environment, line 3421: 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.10',
the complete build log and the output of 'emerge -pqv =dev-python/setuptools-0.6.10'.
The complete build log is located at '/var/tmp/portage/dev-python/setuptools-0.6.10/temp/build.log'.
The ebuild environment file is located at '/var/tmp/portage/dev-python/setuptools-0.6.10/temp/environment'.
S: '/var/tmp/portage/dev-python/setuptools-0.6.10/work/distribute-0.6.10'
From the build.log:
copying tests/shlib_test/hello.c -> build/src/tests/shlib_test
copying tests/shlib_test/hellolib.c -> build/src/tests/shlib_test
copying tests/shlib_test/hello.pyx -> build/src/tests/shlib_test
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.10 failed:
* Building failed with CPython 3.1 in distutils_building() function
*
* Call stack:
* ebuild.sh, line 54: Called src_compile
* environment, line 4643: Called distutils_src_compile
* environment, line 1263: Called python_execute_function 'distutils_building'
* environment, line 3421: 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.10',
* the complete build log and the output of 'emerge -pqv =dev-python/setuptools-0.6.10'.
* The complete build log is located at '/var/tmp/portage/dev-python/setuptools-0.6.10/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/setuptools-0.6.10/temp/environment'.
* S: '/var/tmp/portage/dev-python/setuptools-0.6.10/work/distribute-0.6.10'
dev-python/setuptools-0.6.10 was built with the following:
USE=""
solfire:/>emerge -pqv "=dev-python/setuptools-0.6.10"
[ebuild R ] dev-python/setuptools-0.6.10
How can I successfully run python-updater and proceed in
complete the installation of my new Gentoo system?
PS:
I wrote this mail from my "old" Gentoo system (same hardware)
while in the background blender was rendering a scene. Both
cores were at 100% load for a longer period of time. Everything
remains stable so I do not think, that the hardware is guilty...
Thank you very much in advance for any help!
Best regards
mcc
--
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.
It seems that running lafilefixer had fix the
problem, since revdep-rebuild doesn not reports
any problems.
BUT:
"setup-tools" still fail to compile:
Any idea, how to fix it that ?
Best regards and have a nice sunday!
mcc
* Building of dev-python/setuptools-0.6.10 with CPython 3.1...
python3.1 setup.py build -b build-3.1
creating build
creating build/src
creating build/src/docs
creating build/src/docs/_theme
creating build/src/docs/_theme/nature
creating build/src/docs/_theme/nature/static
creating build/src/docs/build
creating build/src/docs/build/html
creating build/src/docs/build/html/_sources
creating build/src/docs/build/html/_static
creating build/src/setuptools
creating build/src/setuptools/command
creating build/src/setuptools/tests
creating build/src/tests
creating build/src/tests/shlib_test
copying setuptools/dist.py -> build/src/setuptools
copying setuptools/__init__.py -> build/src/setuptools
copying setuptools/sandbox.py -> build/src/setuptools
copying setuptools/package_index.py -> build/src/setuptools
copying setuptools/archive_util.py -> build/src/setuptools
copying setuptools/depends.py -> build/src/setuptools
copying setuptools/extension.py -> build/src/setuptools
copying setuptools/tests/doctest.py -> build/src/setuptools/tests
copying setuptools/tests/test_upload_docs.py -> build/src/setuptools/tests
copying setuptools/tests/test_easy_install.py -> build/src/setuptools/tests
copying setuptools/tests/test_build_ext.py -> build/src/setuptools/tests
copying setuptools/tests/__init__.py -> build/src/setuptools/tests
copying setuptools/tests/test_sandbox.py -> build/src/setuptools/tests
copying setuptools/tests/test_resources.py -> build/src/setuptools/tests
copying setuptools/tests/test_develop.py -> build/src/setuptools/tests
copying setuptools/command/upload.py -> build/src/setuptools/command
copying setuptools/command/setopt.py -> build/src/setuptools/command
copying setuptools/command/install_scripts.py -> build/src/setuptools/command
copying setuptools/command/egg_info.py -> build/src/setuptools/command
copying setuptools/command/upload_docs.py -> build/src/setuptools/command
copying setuptools/command/build_ext.py -> build/src/setuptools/command
copying setuptools/command/__init__.py -> build/src/setuptools/command
copying setuptools/command/install.py -> build/src/setuptools/command
copying setuptools/command/develop.py -> build/src/setuptools/command
copying setuptools/command/build_py.py -> build/src/setuptools/command
copying setuptools/command/saveopts.py -> build/src/setuptools/command
copying setuptools/command/install_lib.py -> build/src/setuptools/command
copying setuptools/command/bdist_wininst.py -> build/src/setuptools/command
copying setuptools/command/easy_install.py -> build/src/setuptools/command
copying setuptools/command/install_egg_info.py -> build/src/setuptools/command
copying setuptools/command/alias.py -> build/src/setuptools/command
copying setuptools/command/bdist_rpm.py -> build/src/setuptools/command
copying setuptools/command/register.py -> build/src/setuptools/command
copying setuptools/command/sdist.py -> build/src/setuptools/command
copying setuptools/command/rotate.py -> build/src/setuptools/command
copying setuptools/command/test.py -> build/src/setuptools/command
copying setuptools/command/bdist_egg.py -> build/src/setuptools/command
copying setuptools/tests/win_script_wrapper.txt -> build/src/setuptools/tests
copying setuptools/cli.exe -> build/src/setuptools
copying setuptools/gui.exe -> build/src/setuptools
copying tests/test_distribute_setup.py -> build/src/tests
copying tests/install_test.py -> build/src/tests
copying tests/shlib_test/setup.py -> build/src/tests/shlib_test
copying tests/shlib_test/test_hello.py -> build/src/tests/shlib_test
copying tests/shlib_test/hello.c -> build/src/tests/shlib_test
copying tests/shlib_test/hellolib.c -> build/src/tests/shlib_test
copying tests/shlib_test/hello.pyx -> build/src/tests/shlib_test
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.10 failed:
* Building failed with CPython 3.1 in distutils_building() function
*
* Call stack:
* ebuild.sh, line 54: Called src_compile
* environment, line 4640: Called distutils_src_compile
* environment, line 1260: Called python_execute_function 'distutils_building'
* environment, line 3418: 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.10',
* the complete build log and the output of 'emerge -pqv =dev-python/setuptools-0.6.10'.
* The complete build log is located at '/var/tmp/portage/dev-python/setuptools-0.6.10/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/setuptools-0.6.10/temp/environment'.
* S: '/var/tmp/portage/dev-python/setuptools-0.6.10/work/distribute-0.6.10'
* Messages for package dev-python/setuptools-0.6.10:
* ERROR: dev-python/setuptools-0.6.10 failed:
* Building failed with CPython 3.1 in distutils_building() function
*
* Call stack:
* ebuild.sh, line 54: Called src_compile
* environment, line 4640: Called distutils_src_compile
* environment, line 1260: Called python_execute_function 'distutils_building'
* environment, line 3418: 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.10',
* the complete build log and the output of 'emerge -pqv =dev-python/setuptools-0.6.10'.
* The complete build log is located at '/var/tmp/portage/dev-python/setuptools-0.6.10/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-python/setuptools-0.6.10/temp/environment'.
* S: '/var/tmp/portage/dev-python/setuptools-0.6.10/work/distribute-0.6.10'
*
* The following package has failed to build or install:
*
* ('ebuild', '/', 'dev-python/setuptools-0.6.10', 'merge'), Log file:
* '/var/tmp/portage/dev-python/setuptools-0.6.10/temp/build.log'
*
* GNU info directory index is up-to-date.
--
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.
06-06-2010, 10:45 AM
Manuel Klemenz
Fatal problem: Pyton-updater "kills" PC
does this happen in combination with the python-updater?
if not, following lines could indicate the prob:
> * Building of dev-python/setuptools-0.6.10 with CPython 3.1...
> python3.1 setup.py build -b build-3.1
did you already switch to 3.1 python slot as your "main" python version?
# eselect python list
As I remember, there's also an eselect news item that recommends not doing so
(some packages are not yet ported/fully compatible)...
Fatal problem: Pyton-updater "kills" PC
