1 |
Hi, |
2 |
I am using catalyst to build a generalized stage4 that will be installed on |
3 |
several machines. The stage4 used to build correctly, however I have since |
4 |
updated the seed stage3 and portage snapshot to keep the stag4 up to date. |
5 |
It seems that certain packages will not build due to issues with the |
6 |
stage3's python. Recent stage3s do not have python2. For example if I try |
7 |
to build a stage4 with dev-python/suds, I get the following error: |
8 |
|
9 |
>>> Emerging (1 of 46) dev-python/suds-0.4 |
10 |
>>> Failed to emerge dev-python/suds-0.4, Log file: |
11 |
>>> '/var/tmp/portage/dev-python/suds-0.4/temp/build.log' |
12 |
* Package: dev-python/suds-0.4 |
13 |
* Repository: gentoo |
14 |
* Maintainer: cedk@g.o python@g.o |
15 |
* USE: amd64 elibc_glibc kernel_linux multilib userland_GNU |
16 |
* FEATURES: sandbox |
17 |
* Building of dev-python/suds-0.4 with CPython 2.7... |
18 |
python2.7 setup.py build -b build-2.7 |
19 |
Traceback (most recent call last): |
20 |
File "setup.py", line 21, in <module> |
21 |
from setuptools import setup, find_packages |
22 |
ImportError: No module named setuptools |
23 |
* ERROR: dev-python/suds-0.4 failed (compile phase): |
24 |
* Building failed with CPython 2.7 in distutils_building() function |
25 |
* |
26 |
* Call stack: |
27 |
* ebuild.sh, line 85: Called src_compile |
28 |
* environment, line 3726: Called distutils_src_compile |
29 |
* environment, line 1043: Called python_execute_function |
30 |
'distutils_building' |
31 |
* environment, line 2110: Called die |
32 |
* The specific snippet of code: |
33 |
* die "${failure_message}"; |
34 |
* |
35 |
* If you need support, post the output of 'emerge --info |
36 |
=dev-python/suds-0.4', |
37 |
* the complete build log and the output of 'emerge -pqv |
38 |
=dev-python/suds-0.4'. |
39 |
* The complete build log is located at |
40 |
'/var/tmp/portage/dev-python/suds-0.4/temp/build.log'. |
41 |
* The ebuild environment file is located at |
42 |
'/var/tmp/portage/dev-python/suds-0.4/temp/environment'. |
43 |
* S: '/var/tmp/portage/dev-python/suds-0.4/work/suds-0.4' |
44 |
|
45 |
* Messages for package dev-python/suds-0.4: |
46 |
|
47 |
* ERROR: dev-python/suds-0.4 failed (compile phase): |
48 |
* Building failed with CPython 2.7 in distutils_building() function |
49 |
* |
50 |
* Call stack: |
51 |
* ebuild.sh, line 85: Called src_compile |
52 |
* environment, line 3726: Called distutils_src_compile |
53 |
* environment, line 1043: Called python_execute_function |
54 |
'distutils_building' |
55 |
* environment, line 2110: Called die |
56 |
* The specific snippet of code: |
57 |
* die "${failure_message}"; |
58 |
* |
59 |
* If you need support, post the output of 'emerge --info |
60 |
=dev-python/suds-0.4', |
61 |
* the complete build log and the output of 'emerge -pqv |
62 |
=dev-python/suds-0.4'. |
63 |
* The complete build log is located at |
64 |
'/var/tmp/portage/dev-python/suds-0.4/temp/build.log'. |
65 |
* The ebuild environment file is located at |
66 |
'/var/tmp/portage/dev-python/suds-0.4/temp/environment'. |
67 |
* S: '/var/tmp/portage/dev-python/suds-0.4/work/suds-0.4' |
68 |
|
69 |
When I look in the temp directory for this build, it seems that python2.7 |
70 |
is installed. setuptools is also installed but only for python3. Is there |
71 |
a way to have catalyst build setuptools for python2? Is there a way to |
72 |
switch the system python to 2.7 or should it stay as python3? Or is this |
73 |
not really a catalyst issue and rather an issue with the suds ebuild? Is |
74 |
there any other info that would be helpful? |
75 |
|
76 |
Thanks, |
77 |
|
78 |
-- Tim Messier |