From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.77) (envelope-from ) id 1SoII6-0000dv-KL for garchives@archives.gentoo.org; Mon, 09 Jul 2012 18:02:34 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 13129E06E8 for ; Mon, 9 Jul 2012 18:02:33 +0000 (UTC) Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by pigeon.gentoo.org (Postfix) with ESMTP id A03A9E06C0 for ; Mon, 9 Jul 2012 15:12:04 +0000 (UTC) Received: by lbbgk8 with SMTP id gk8so17158022lbb.40 for ; Mon, 09 Jul 2012 08:12:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=7GA+CAo5Q6bwavOpJP93nRqU/vl6rhWb44FvIhbXNSQ=; b=kp7W6N20fhKmOuOGTU2RewZ25mvq9UuPmcU028BEBkyKBNEQB4Tn17eRF0sFmewkQH wyoAnszXuNjRtFC92nJqgek1jB1LBSQOK/vDKH88Uu6LfThlvmcLV4xqc1Fz0KnrqVEJ 0zX13suRDFifTTnoJrxfrvwuFRiIIQSlSi3HJ6fxvJsIcN4TRmW4NQHEtzVe+9+cmvrn q1ZOrTlA9YDOYw/g0mEOdXBHA7m74F0c6F1zfGLp4+5btXfsZsvtYsEvZZ9kwtkt86Hm LZXmjeC46b20rCM9EIyBPWJPKYY4oTK9KfxAc1xqLJdCp5e9r35ykkhOaTTzhdlkQX9Q qxig== Received: by 10.112.49.227 with SMTP id x3mr18572180lbn.73.1341846723634; Mon, 09 Jul 2012 08:12:03 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org MIME-Version: 1.0 Received: by 10.152.129.233 with HTTP; Mon, 9 Jul 2012 08:11:43 -0700 (PDT) From: Tim Messier Date: Mon, 9 Jul 2012 15:11:43 +0000 Message-ID: Subject: [gentoo-catalyst] Stage 4 build issues To: gentoo-catalyst@lists.gentoo.org Content-Type: multipart/alternative; boundary=bcaec554dd364e24bc04c467099c X-Archives-Salt: c5b49a63-2e0d-4fc8-a305-8238e6b1023c X-Archives-Hash: 16f6a07b90c3f927f6644698727236e5 --bcaec554dd364e24bc04c467099c Content-Type: text/plain; charset=ISO-8859-1 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 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? Thanks, -- Tim Messier --bcaec554dd364e24bc04c467099c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,
I am using catalyst to build a generalized stage4 that will be insta= lled on several machines. The stage4 used to build correctly, however I hav= e since updated the seed stage3 and portage snapshot to keep the stag4 up t= o date. It seems that certain packages will not build due to issues with th= e 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
>>> Fai= led to emerge dev-python/suds-0.4, Log file:
>>>=A0 '/var/t= mp/portage/dev-python/suds-0.4/temp/build.log'
=A0* Package:=A0=A0= =A0 dev-python/suds-0.4
=A0* Repository: gentoo
=A0* Maintainer: cedk@gentoo.org python@gentoo.org
=A0* USE:=A0=A0=A0=A0=A0=A0= =A0 amd64 elibc_glibc kernel_linux multilib userland_GNU
=A0* FEATURES:=A0=A0 sandbox
=A0* Building of dev-python/suds-0.4 with C= Python 2.7...
python2.7 setup.py build -b build-2.7
Traceback (most r= ecent call last):
=A0 File "setup.py", line 21, in <module&= gt;
=A0=A0=A0 from setuptools import setup, find_packages
ImportError: No mo= dule named setuptools
=A0* ERROR: dev-python/suds-0.4 failed (compile ph= ase):
=A0*=A0=A0 Building failed with CPython 2.7 in distutils_building(= ) function
=A0*
=A0* Call stack:
=A0*=A0=A0=A0=A0 ebuild.sh, line=A0=A0 85:=A0 = Called src_compile
=A0*=A0=A0 environment, line 3726:=A0 Called distutil= s_src_compile
=A0*=A0=A0 environment, line 1043:=A0 Called python_execut= e_function 'distutils_building'
=A0*=A0=A0 environment, line 2110:=A0 Called die
=A0* The specific snipp= et of code:
=A0*=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0 die "${failure_message}";
=A0*
=A0* If you ne= ed support, post the output of 'emerge --info =3Ddev-python/suds-0.4= 9;,
=A0* the complete build log and the output of 'emerge -pqv =3Ddev-pytho= n/suds-0.4'.
=A0* The complete build log is located at '/var/tmp= /portage/dev-python/suds-0.4/temp/build.log'.
=A0* The ebuild enviro= nment file is located at '/var/tmp/portage/dev-python/suds-0.4/temp/env= ironment'.
=A0* S: '/var/tmp/portage/dev-python/suds-0.4/work/suds-0.4'
=A0* Messages for package dev-python/suds-0.4:

=A0* ERROR: dev-pyth= on/suds-0.4 failed (compile phase):
=A0*=A0=A0 Building failed with CPyt= hon 2.7 in distutils_building() function
=A0*
=A0* Call stack:
=A0*=A0=A0=A0=A0 ebuild.sh, line=A0=A0 85:=A0 = Called src_compile
=A0*=A0=A0 environment, line 3726:=A0 Called distutil= s_src_compile
=A0*=A0=A0 environment, line 1043:=A0 Called python_execut= e_function 'distutils_building'
=A0*=A0=A0 environment, line 2110:=A0 Called die
=A0* The specific snipp= et of code:
=A0*=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0= =A0=A0=A0=A0 die "${failure_message}";
=A0*
=A0* If you ne= ed support, post the output of 'emerge --info =3Ddev-python/suds-0.4= 9;,
=A0* the complete build log and the output of 'emerge -pqv =3Ddev-pytho= n/suds-0.4'.
=A0* The complete build log is located at '/var/tmp= /portage/dev-python/suds-0.4/temp/build.log'.
=A0* The ebuild enviro= nment file is located at '/var/tmp/portage/dev-python/suds-0.4/temp/env= ironment'.
=A0* 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.=A0 Is ther= e a way to have catalyst build setuptools for python2?=A0 Is there a way to= switch the system python to 2.7 or should it stay as python3? Or is this n= ot really a catalyst issue and rather an issue with the suds ebuild? Is the= re any other info that would be helpful?

=A0Thanks,

-- Tim Messier
--bcaec554dd364e24bc04c467099c--