public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Compilation aborted for setuptools-0.6.12
Date: Sun, 20 Jun 2010 01:38:34 +0200	[thread overview]
Message-ID: <20100619233834.GA4890@solfire> (raw)
In-Reply-To: <4C1D0CAE.5020404@gmail.com>

Dale <rdalek1967@gmail.com> [10-06-20 01:33]:
> Alan McKinnon wrote:
> >On Saturday 19 June 2010 18:06:58 meino.cramer@gmx.de wrote:
> >   
> >>David W Noon<dwnoon@ntlworld.com>  [10-06-19 18:00]:
> >>     
> >>>On Sat, 19 Jun 2010 17:00:02 +0200, meino.cramer@gmx.de wrote about 
> >>>Re:
> >>>
> >>>[gentoo-user] Re: Compilation aborted for setuptools-0.6.12:
> >>>       
> >>>>walt<w41ter@gmail.com>  [10-06-19 16:48]:
> >>>>         
> >>>[snip]
> >>>
> >>>       
> >>>>>Have you set eselect python to use python-3 instead of python-2?  
> >>>>>If
> >>>>>so,
> >>>>>try setting it back to python-2.
> >>>>>           
> >>>>No, python 2.6 ist set according to the output of
> >>>>
> >>>>    eselect python list
> >>>>
> >>>>python 3.1 is installed but not selected.
> >>>>
> >>>>What else can produce this compilation error?
> >>>>         
> >>>Have you run python-updater?
> >>>
> >>>When new packages have Python components, they will build both 2.6 
> >>>and
> >>>3.1 modules if possible.  This means that their dependencies also 
> >>>need
> >>>to have both 2.6 and 3.1 modules.  You achieve this by running
> >>>python-updater; this can take several hours.
> >>>       
> >>Hi Dave,
> >>
> >>wait...hopefully I understand this correctly, before I start to screw
> >>up my newly installed system...
> >>
> >>State 1 right after installing Gentoo: Pyton2.6 selected, installed
> >>and up.
> >>State 2 some days later while upateing python3.1 was offered but
> >>should *not* eselect python 3.1 since some older package are still
> >>not updated to work correctly with 3.1
> >>State 3 setuptools seems to try to compile against 3.1 and failed.
> >>
> >>Now I should run python-updater to ... (scratching my head)?
> >>To update to python 3.1..but setuptools failed while compiling
> >>against python 3.1
> >>
> >>It seems I myself feel a little screwed up,,, ;)
> >>
> >>?
> >>
> >>Best regards,
> >>mcc
> >>     
> >Did you miss the significance of this part?
> >
> >"This means that their dependencies also need to have both 2.6 and 3.1
> >modules.  You achieve this by running python-updater; this can take 
> >several
> >hours."
> >
> >   
> 
> Or if he doesn't really need python 3, he can just mask the thing until 
> he does need it.  Of course, he may have to run python-updater again or 
> rebuild the same packages again to get them to not use python 3.
> 
> Yep, making this stable hasn't confused anyone yet.  o_O
> 
> Dale
> 
> :-)  :-)
> 

Ok, I run python-updater and It fails with (guess...drumroll):



 * 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 4627:  Called distutils_src_compile
 *   environment, line 1257:  Called python_execute_function 'distutils_building'
 *   environment, line 3405:  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'
 *
 * The following package has failed to build or install:
 *
 *  ('ebuild', '/', 'dev-python/setuptools-0.6.12', 'merge'), Log file:
 *   '/var/tmp/portage/dev-python/setuptools-0.6.12/temp/build.log'
 *


And yes: I need python 3.1 (building the svn version of blender needs
it, which gets installed under /uss/local/...)

Is this the infamous cat, which bits into its own tail... ?

Best regards,
mcc






  reply	other threads:[~2010-06-20  0:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <eX0OK-2wa-5@gated-at.bofh.it>
     [not found] ` <eX7wR-3Qg-7@gated-at.bofh.it>
     [not found]   ` <eX7Gy-425-3@gated-at.bofh.it>
2010-06-19 15:56     ` [gentoo-user] Re: Compilation aborted for setuptools-0.6.12 David W Noon
2010-06-19 16:06       ` meino.cramer
2010-06-19 17:54         ` Alan McKinnon
2010-06-19 18:30           ` Dale
2010-06-19 23:38             ` meino.cramer [this message]
2010-06-20  1:18               ` David Abbott
2010-06-20  2:59                 ` meino.cramer
     [not found] <eX8CC-5rD-21@gated-at.bofh.it>
     [not found] ` <eX8CC-5rD-23@gated-at.bofh.it>
     [not found]   ` <eX8CC-5rD-25@gated-at.bofh.it>
     [not found]     ` <eX8CC-5rD-19@gated-at.bofh.it>
     [not found]       ` <eX8Mi-5Tf-19@gated-at.bofh.it>
2010-06-19 17:44         ` David W Noon
2010-06-19  7:37 [gentoo-user] " meino.cramer
2010-06-19 14:43 ` [gentoo-user] " walt
2010-06-19 14:55   ` meino.cramer
2010-06-20 17:07     ` walt
2010-06-20 17:34       ` meino.cramer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100619233834.GA4890@solfire \
    --to=meino.cramer@gmx.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox