Hi,
I am using catalyst to build a generalized stage4 that will be installed on several machines. The stage4 used to build correctly, however I have since updated the seed stage3 and portage snapshot to keep the stag4 up to date. It seems that certain packages will not build due to issues with the stage3's python. Recent stage3s do not have python2. For example if I try to build a stage4 with dev-python/suds, I get the following error:
>>> Emerging (1 of 46) dev-python/suds-0.4
>>> Failed to emerge dev-python/suds-0.4, Log file:
>>>* '/var/tmp/portage/dev-python/suds-0.4/temp/build.log'
** Package:*** dev-python/suds-0.4
** FEATURES:** sandbox
** Building of dev-python/suds-0.4 with CPython 2.7...
python2.7 setup.py build -b build-2.7
Traceback (most recent call last):
* File "setup.py", line 21, in <module>
*** from setuptools import setup, find_packages
ImportError: No module named setuptools
** ERROR: dev-python/suds-0.4 failed (compile phase):
**** Building failed with CPython 2.7 in distutils_building() function
**
** Call stack:
****** ebuild.sh, line** 85:* Called src_compile
**** environment, line 3726:* Called distutils_src_compile
**** environment, line 1043:* Called python_execute_function 'distutils_building'
**** environment, line 2110:* Called die
** The specific snippet of code:
************************ die "${failure_message}";
**
** If you need support, post the output of 'emerge --info =dev-python/suds-0.4',
** the complete build log and the output of 'emerge -pqv =dev-python/suds-0.4'.
** The complete build log is located at '/var/tmp/portage/dev-python/suds-0.4/temp/build.log'.
** The ebuild environment file is located at '/var/tmp/portage/dev-python/suds-0.4/temp/environment'.
** ERROR: dev-python/suds-0.4 failed (compile phase):
**** Building failed with CPython 2.7 in distutils_building() function
**
** Call stack:
****** ebuild.sh, line** 85:* Called src_compile
**** environment, line 3726:* Called distutils_src_compile
**** environment, line 1043:* Called python_execute_function 'distutils_building'
**** environment, line 2110:* Called die
** The specific snippet of code:
************************ die "${failure_message}";
**
** If you need support, post the output of 'emerge --info =dev-python/suds-0.4',
** the complete build log and the output of 'emerge -pqv =dev-python/suds-0.4'.
** The complete build log is located at '/var/tmp/portage/dev-python/suds-0.4/temp/build.log'.
** The ebuild environment file is located at '/var/tmp/portage/dev-python/suds-0.4/temp/environment'.
When I look in the temp directory for this build, it seems that python2.7 is installed. setuptools is also installed but only for python3.* Is there a way to have catalyst build setuptools for python2?* Is there a way to switch the system python to 2.7 or should it stay as python3? Or is this not really a catalyst issue and rather an issue with the suds ebuild? Is there any other info that would be helpful?
*Thanks,
-- Tim Messier
07-09-2012, 04:53 PM
Sebastian Pipping
Stage 4 build issues
Hello Tim,
it sounds like you need to specify USE_PYTHON and run python-updater to
fix that issue.
it sounds like you need to specify USE_PYTHON and run python-updater to
fix that issue.
Here is my current confguration:
* # fgrep USE_PYTHON /etc/make.conf
* USE_PYTHON="2.6 2.7 3.1 3.2"
Best,
Sebastian
07-09-2012, 10:15 PM
"Jorge Manuel B. S. Vicetto"
Stage 4 build issues
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 09-07-2012 15:11, Tim Messier wrote:
> Hi, I am using catalyst to build a generalized stage4 that will be
> installed on several machines. The stage4 used to build correctly,
> however I have since updated the seed stage3 and portage snapshot
> to keep the stag4 up to date. It seems that certain packages will
> not build due to issues with the stage3's python. Recent stage3s do
> not have python2. For example if I try to build a stage4 with
> dev-python/suds, I get the following error:
>
>>>> Emerging (1 of 46) dev-python/suds-0.4 Failed to emerge
>>>> dev-python/suds-0.4, Log file:
>>>> '/var/tmp/portage/dev-python/suds-0.4/temp/build.log'
> * Package: dev-python/suds-0.4 * Repository: gentoo *
> Maintainer: cedk@gentoo.org python@gentoo.org * USE: amd64
> elibc_glibc kernel_linux multilib userland_GNU * FEATURES:
> sandbox * Building of dev-python/suds-0.4 with CPython 2.7...
> python2.7 setup.py build -b build-2.7 Traceback (most recent call
> last): File "setup.py", line 21, in <module> from setuptools import
> setup, find_packages ImportError: No module named setuptools *
> ERROR: dev-python/suds-0.4 failed (compile phase): * Building
> failed with CPython 2.7 in distutils_building() function * * Call
> stack: * ebuild.sh, line 85: Called src_compile *
> environment, line 3726: Called distutils_src_compile *
> environment, line 1043: Called python_execute_function
> 'distutils_building' * environment, line 2110: Called die * The
> specific snippet of code: * die
> "${failure_message}"; * * If you need support, post the output of
> 'emerge --info =dev-python/suds-0.4', * the complete build log and
> the output of 'emerge -pqv =dev-python/suds-0.4'. * The complete
> build log is located at
> '/var/tmp/portage/dev-python/suds-0.4/temp/build.log'. * The ebuild
> environment file is located at
> '/var/tmp/portage/dev-python/suds-0.4/temp/environment'. * S:
> '/var/tmp/portage/dev-python/suds-0.4/work/suds-0.4'
>
> * Messages for package dev-python/suds-0.4:
>
> * ERROR: dev-python/suds-0.4 failed (compile phase): * Building
> failed with CPython 2.7 in distutils_building() function * * Call
> stack: * ebuild.sh, line 85: Called src_compile *
> environment, line 3726: Called distutils_src_compile *
> environment, line 1043: Called python_execute_function
> 'distutils_building' * environment, line 2110: Called die * The
> specific snippet of code: * die
> "${failure_message}"; * * If you need support, post the output of
> 'emerge --info =dev-python/suds-0.4', * the complete build log and
> the output of 'emerge -pqv =dev-python/suds-0.4'. * The complete
> build log is located at
> '/var/tmp/portage/dev-python/suds-0.4/temp/build.log'. * The ebuild
> environment file is located at
> '/var/tmp/portage/dev-python/suds-0.4/temp/environment'. * S:
> '/var/tmp/portage/dev-python/suds-0.4/work/suds-0.4'
>
> When I look in the temp directory for this build, it seems that
> python2.7 is installed. setuptools is also installed but only for
> python3. Is there a way to have catalyst build setuptools for
> python2? Is there a way to switch the system python to 2.7 or
> should it stay as python3? Or is this not really a catalyst issue
> and rather an issue with the suds ebuild? Is there any other info
> that would be helpful?
This is an issue with this particular package. Please file a bug in
Gentoo Bugzilla and assign it to the package maintainers. Let them
know that the package fails to build when the user only has python-3
installed.
On 07/10/2012 12:15 AM, Jorge Manuel B. S. Vicetto wrote:
>> * ERROR: dev-python/suds-0.4 failed (compile phase): *
>> Building failed with CPython 2.7 in distutils_building() function
>> [..]
>
> This is an issue with this particular package. Please file a bug
> in Gentoo Bugzilla and assign it to the package maintainers. Let
> them know that the package fails to build when the user only has
> python-3 installed.
The quote at the very top look like Python 2.7 is installed, too.
Best,
Sebastian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Yea python2.7 is installed. But the system default python is 3.2 and setuptools is built only for 3. Suds is trying to use python2 (It has a restrict on python 3.*) but is failing due to setuptools not being rebuilt for python2. I will file a bug with for the package maintainers, but I am not sure what they can do about it if suds is not ready for python3...
-- Timothy Messier
On Jul 9, 2012 7:02 PM, "Sebastian Pipping" <sping@gentoo.org> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/10/2012 12:15 AM, Jorge Manuel B. S. Vicetto wrote:
Tim Messier wrote:
> I will file a bug with for the package maintainers, but I am not
> sure what they can do about it if suds is not ready for python3...
I think the ebuild may just need to set PYTHON_DEPEND,
SUPPORT_PYTHON_ABIS, and RESTRICT_PYTHON_ABIS.
//Peter
07-10-2012, 12:52 AM
Tim Messier
Stage 4 build issues
It looks like those vars are already set
On Jul 9, 2012 8:50 PM, "Peter Stuge" <peter@stuge.se> wrote:
Tim Messier wrote:
> I will file a bug with for the package maintainers, but I am not
> sure what they can do about it if suds is not ready for python3...
I think the ebuild may just need to set PYTHON_DEPEND,
Stage 4 build issues
