[gentoo-user] Compilation aborted for setuptools-0.6.12

[gentoo-user] Compilation aborted for setuptools-0.6.12

[meino.cramer]

Hi,

compilation of setuptools-0.6.12 aborts woth:
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.12 failed:
 *   Building failed with CPython 3.1 in distutils_building() function
 *
 * Call stack:
 *     ebuild.sh, line   54:  Called src_compile
 *   environment, line 4648:  Called distutils_src_compile
 *   environment, line 1278:  Called python_execute_function 'distutils_building'
 *   environment, line 3426:  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'

>>> Failed to emerge dev-python/setuptools-0.6.12, Log file:

>>>  '/var/tmp/portage/dev-python/setuptools-0.6.12/temp/build.log'

 * 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 4648:  Called distutils_src_compile
 *   environment, line 1278:  Called python_execute_function 'distutils_building'
 *   environment, line 3426:  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'
solfire:/root>qsearch setuptools
search: Updating ebuild cache ...
search: Finished 27398 entries in 0.474906 seconds
dev-python/setuptools Distribute (fork of Setuptools) is a collection of extensions to Distutils

f you need the addtional files mentioned above please dont hesitat to
mail me.
I only dont with to clutter the mailing list.

How can I fix that bug?

Best regards.
mcc

[gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[walt]

On 06/19/2010 12:37 AM, meino.cramer@gmx.de wrote:
>
> Hi,
>
> compilation of setuptools-0.6.12 aborts woth:
> 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>

Have you set eselect python to use python-3 instead of python-2?  If so,
try setting it back to python-2.

Re: [gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[meino.cramer]

walt <w41ter@gmail.com> [10-06-19 16:48]:
> On 06/19/2010 12:37 AM, meino.cramer@gmx.de wrote:
> >
> >Hi,
> >
> >compilation of setuptools-0.6.12 aborts woth:
> >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>
> 
> 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?

Best regards,
mcc

Re: [gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[David W Noon]

[-- Attachment #1: Type: text/plain, Size: 997 bytes --]

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.
-- 
Regards,

Dave  [RLU #314465]
======================================================================
dwnoon@ntlworld.com (David W Noon)
======================================================================

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[meino.cramer]

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.
> -- 
> Regards,
> 
> Dave  [RLU #314465]
> ======================================================================
> dwnoon@ntlworld.com (David W Noon)
> ======================================================================


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

Re: [gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[David W Noon]

[-- Attachment #1: Type: text/plain, Size: 1417 bytes --]

On Sat, 19 Jun 2010 18:10:02 +0200, meino.cramer@gmx.de wrote about Re:
[gentoo-user] Re: Compilation aborted for setuptools-0.6.12:

[snip]
>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)?

You need to run python-updater so that there are python modules for all
packages that are compatible with both releases of Python.  This is
because any such package will attempt to build modules for both Python
interpreters, even though you are currently using only 2.6.

>To update to python 3.1..but setuptools failed while compiling 
>against python 3.1

Just run python-updater first, as this will take care of any
build-time dependencies of setuptools. Then try to emerge your general
updates, which should build setuptools correctly.
-- 
Regards,

Dave  [RLU #314465]
======================================================================
dwnoon@ntlworld.com (David W Noon)
======================================================================

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[Alan McKinnon]

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."

-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[Dale]

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

:-)  :-)

Re: [gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[meino.cramer]

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

Re: [gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[David Abbott]

On Sat, Jun 19, 2010 at 7:38 PM,  <meino.cramer@gmx.de> wrote:
> 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
>

You can set your main active version of python as 2.6, and still have
3.1 installed to build and run Blender.
http://www.gentoo.org/proj/en/Python/developersguide.xml

I have not seen the ebuild you are using for your svn version of
blender so not sure if it will work as is.
Python is not ready as yet to run as your main active version yet and
looks like you found one of the reasons.

-- 
David Abbott (dabbott)

Re: [gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[meino.cramer]

David Abbott <david@pythontoo.com> [10-06-20 04:51]:
> On Sat, Jun 19, 2010 at 7:38 PM,  <meino.cramer@gmx.de> wrote:
> > 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
> >
> 
> You can set your main active version of python as 2.6, and still have
> 3.1 installed to build and run Blender.
> http://www.gentoo.org/proj/en/Python/developersguide.xml
> 
> I have not seen the ebuild you are using for your svn version of
> blender so not sure if it will work as is.
> Python is not ready as yet to run as your main active version yet and
> looks like you found one of the reasons.
> 
> -- 
> David Abbott (dabbott)
> 


May I cite myself from a previous posting into this thread:

> 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?
> 
> Best regards,
> mcc
> 


I am not using an ebuild for the svn-version of Blender.
It is compiled "outside" Gentoo, installed under /usr/local 
and the only thing, which may have "system-impact" (...) is
one big executable: Blender itsself. The whole thing cant
have any influence on the rest of the system.

And as said, eselect reports:

eselect python list
Available Python interpreters:
  [1]   python2.6 *
  [2]   python3.1

Best regards,
mcc

Re: [gentoo-user] Compilation aborted for setuptools-0.6.12

[Arttu V.]

On 6/19/10, meino.cramer@gmx.de <meino.cramer@gmx.de> wrote:
>
> Hi,
>
> compilation of setuptools-0.6.12 aborts woth:
> 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'

Over here it seems to run a piece printing out messages starting with
"RefactoringTool:" where it fails for you. AFAICT, 2to3-refactoring
stuff is part of dev-lang/python package itself.

So, I wonder if "emerge -1 python:2.6" would help? (Or grabbing a
pre-compiled binary from tinderbox.dev.gentoo.org if the emerge
fails.)

-- 
Arttu V.

Re: [gentoo-user] Compilation aborted for setuptools-0.6.12

[meino.cramer]

Arttu V. <arttuv69@gmail.com> [10-06-20 12:28]:
> On 6/19/10, meino.cramer@gmx.de <meino.cramer@gmx.de> wrote:
> >
> > Hi,
> >
> > compilation of setuptools-0.6.12 aborts woth:
> > 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'
> 
> Over here it seems to run a piece printing out messages starting with
> "RefactoringTool:" where it fails for you. AFAICT, 2to3-refactoring
> stuff is part of dev-lang/python package itself.
> 
> So, I wonder if "emerge -1 python:2.6" would help? (Or grabbing a
> pre-compiled binary from tinderbox.dev.gentoo.org if the emerge
> fails.)
> 
> -- 
> Arttu V.
> 

Hi Arttu,

thanks for your posting! :)

Python2.6 compiles fine, setuptool fails again at the same point...

What can I try next?

Have a nice weekend!
Best regards,
mcc

Re: [gentoo-user] Compilation aborted for setuptools-0.6.12

[Arttu V.]

On 6/20/10, meino.cramer@gmx.de <meino.cramer@gmx.de> wrote:
> Arttu V. <arttuv69@gmail.com> [10-06-20 12:28]:
>> On 6/19/10, meino.cramer@gmx.de <meino.cramer@gmx.de> wrote:
>> >
>> > Hi,
>> >
>> > compilation of setuptools-0.6.12 aborts woth:
>> > 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'
>>
>> Over here it seems to run a piece printing out messages starting with
>> "RefactoringTool:" where it fails for you. AFAICT, 2to3-refactoring
>> stuff is part of dev-lang/python package itself.
>>
>> So, I wonder if "emerge -1 python:2.6" would help? (Or grabbing a
>> pre-compiled binary from tinderbox.dev.gentoo.org if the emerge
>> fails.)
>>
>> --
>> Arttu V.
>>
>
> Hi Arttu,
>
> thanks for your posting! :)
>
> Python2.6 compiles fine, setuptool fails again at the same point...
>
> What can I try next?

Short of recompiling also python 3.1 (with distcc, ccache and such
possible interference disabled) -- I'm out out ideas.

-- 
Arttu V.

Re: [gentoo-user] Compilation aborted for setuptools-0.6.12

[meino.cramer]

Arttu V. <arttuv69@gmail.com> [10-06-20 14:04]:
> On 6/20/10, meino.cramer@gmx.de <meino.cramer@gmx.de> wrote:
> > Arttu V. <arttuv69@gmail.com> [10-06-20 12:28]:
> >> On 6/19/10, meino.cramer@gmx.de <meino.cramer@gmx.de> wrote:
> >> >
> >> > Hi,
> >> >
> >> > compilation of setuptools-0.6.12 aborts woth:
> >> > 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'
> >>
> >> Over here it seems to run a piece printing out messages starting with
> >> "RefactoringTool:" where it fails for you. AFAICT, 2to3-refactoring
> >> stuff is part of dev-lang/python package itself.
> >>
> >> So, I wonder if "emerge -1 python:2.6" would help? (Or grabbing a
> >> pre-compiled binary from tinderbox.dev.gentoo.org if the emerge
> >> fails.)
> >>
> >> --
> >> Arttu V.
> >>
> >
> > Hi Arttu,
> >
> > thanks for your posting! :)
> >
> > Python2.6 compiles fine, setuptool fails again at the same point...
> >
> > What can I try next?
> 
> Short of recompiling also python 3.1 (with distcc, ccache and such
> possible interference disabled) -- I'm out out ideas.
> 
> -- 
> Arttu V.
> 

Hi Arttu,

thanks again for your help ! :)

Tried that...python3.1 compiles fine, setuptools failed.

And now?

Best regards,
mcc

Re: [gentoo-user] Compilation aborted for setuptools-0.6.12

[Alex Schuster]

meino.cramer@gmx.de writes:

> Tried that...python3.1 compiles fine, setuptools failed.
> 
> And now?

How about putting dev-python/setuptools into
/etc/portage/package.keywords, and trying to emerge 0.6.13?

	Wonko

Re: [gentoo-user] Compilation aborted for setuptools-0.6.12

[meino.cramer]

Alex Schuster <wonko@wonkology.org> [10-06-20 15:16]:
> meino.cramer@gmx.de writes:
> 
> > Tried that...python3.1 compiles fine, setuptools failed.
> > 
> > And now?
> 
> How about putting dev-python/setuptools into
> /etc/portage/package.keywords, and trying to emerge 0.6.13?
> 
> 	Wonko
> 

Hi,

thanks for your posting, Wonko! :)

Is there any Changelog-issue in that version, that says anything
related to the compilation problem?

I tried to re-emerge setuptools 0.6.10 and it fails the same way.
So I believe (=not knowing) that this problem is caused by something
outside setuptools, which gets screwed up.

Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10
(current version) is gone and cannot get back due to the same problem
(see above). And then I have a "unstable" version, which may pull in
other unstable versions of something else, which pull in....

This way I have corrupted my last installed gentoo system...

Best regards, 
mcc

Re: [gentoo-user] Compilation aborted for setuptools-0.6.12

[Alex Schuster]

meino.cramer@gmx.de writes:

> Alex Schuster <wonko@wonkology.org> [10-06-20 15:16]:

>> How about putting dev-python/setuptools into
>> /etc/portage/package.keywords, and trying to emerge 0.6.13?

> I tried to re-emerge setuptools 0.6.10 and it fails the same way.
> So I believe (=not knowing) that this problem is caused by something
> outside setuptools, which gets screwed up.

Probably python itself, as Arttu pointed out.


> Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10
> (current version) is gone and cannot get back due to the same problem
> (see above). And then I have a "unstable" version, which may pull in
> other unstable versions of something else, which pull in....

Maybe, but at least in the ebuild itself there are no such dependencies.
If you'd need to keyword this package only, it should do no harm. If
more things need to be keyworded, I agree that this tends to make things
complicated. But at least you can quickpkg the existing version, and get
it back when needed without compiling with emerge -k.
But when 0.6.10 also fails, the problem is likely to be somewhere else.

> This way I have corrupted my last installed gentoo system...

I'm at ~amd64 now, and things are easier now :) At least for me.

If you are desperate: Maybe removing setuptools would at least make
python-updater run through, unless something would pull it in again.
Emerge -k setuptools back. You may be missing stuff for python 3.1, but
maybe this does not harm too much.

And report a bug at bugs.gentoo.org, so the maintainers know what's
going on.

	Wonko

Re: [gentoo-user] Compilation aborted for setuptools-0.6.12

[meino.cramer]

Alex Schuster <wonko@wonkology.org> [10-06-20 17:08]:
> meino.cramer@gmx.de writes:
> 
> > Alex Schuster <wonko@wonkology.org> [10-06-20 15:16]:
> 
> >> How about putting dev-python/setuptools into
> >> /etc/portage/package.keywords, and trying to emerge 0.6.13?
> 
> > I tried to re-emerge setuptools 0.6.10 and it fails the same way.
> > So I believe (=not knowing) that this problem is caused by something
> > outside setuptools, which gets screwed up.
> 
> Probably python itself, as Arttu pointed out.
> 
> 
> > Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10
> > (current version) is gone and cannot get back due to the same problem
> > (see above). And then I have a "unstable" version, which may pull in
> > other unstable versions of something else, which pull in....
> 
> Maybe, but at least in the ebuild itself there are no such dependencies.
> If you'd need to keyword this package only, it should do no harm. If
> more things need to be keyworded, I agree that this tends to make things
> complicated. But at least you can quickpkg the existing version, and get
> it back when needed without compiling with emerge -k.
> But when 0.6.10 also fails, the problem is likely to be somewhere else.
> 
> > This way I have corrupted my last installed gentoo system...
> 
> I'm at ~amd64 now, and things are easier now :) At least for me.
> 
> If you are desperate: Maybe removing setuptools would at least make
> python-updater run through, unless something would pull it in again.
> Emerge -k setuptools back. You may be missing stuff for python 3.1, but
> maybe this does not harm too much.
> 
> And report a bug at bugs.gentoo.org, so the maintainers know what's
> going on.
> 
> 	Wonko
> 

Hi Wonko,

I checked the dependencies. Python-updater would recompile
gnumeric,boost and setuptools.

setuptools will be pulled in last consequence from inkscape and
gnumeric (not directly).

Best regards,
mcc

Re: [gentoo-user] Compilation aborted for setuptools-0.6.12

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1908 bytes --]

On Sunday 20 June 2010 16:05:58 Alex Schuster wrote:
> meino.cramer@gmx.de writes:
> > Alex Schuster <wonko@wonkology.org> [10-06-20 15:16]:
> >> How about putting dev-python/setuptools into
> >> /etc/portage/package.keywords, and trying to emerge 0.6.13?
> >
> > I tried to re-emerge setuptools 0.6.10 and it fails the same way.
> > So I believe (=not knowing) that this problem is caused by something
> > outside setuptools, which gets screwed up.
> 
> Probably python itself, as Arttu pointed out.
> 
> > Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10
> > (current version) is gone and cannot get back due to the same problem
> > (see above). And then I have a "unstable" version, which may pull in
> > other unstable versions of something else, which pull in....
> 
> Maybe, but at least in the ebuild itself there are no such dependencies.
> If you'd need to keyword this package only, it should do no harm. If
> more things need to be keyworded, I agree that this tends to make things
> complicated. But at least you can quickpkg the existing version, and get
> it back when needed without compiling with emerge -k.
> But when 0.6.10 also fails, the problem is likely to be somewhere else.
> 
> > This way I have corrupted my last installed gentoo system...
> 
> I'm at ~amd64 now, and things are easier now :) At least for me.
> 
> If you are desperate: Maybe removing setuptools would at least make
> python-updater run through, unless something would pull it in again.
> Emerge -k setuptools back. You may be missing stuff for python 3.1, but
> maybe this does not harm too much.
> 
> And report a bug at bugs.gentoo.org, so the maintainers know what's
> going on.

I'd have another go but after setting MAKEOPTS="-j1" (although I have to admit 
the error you posted does not look like this would make any difference).
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Compilation aborted for setuptools-0.6.12

[meino.cramer]

Mick <michaelkintzios@gmail.com> [10-06-20 18:38]:
> On Sunday 20 June 2010 16:05:58 Alex Schuster wrote:
> > meino.cramer@gmx.de writes:
> > > Alex Schuster <wonko@wonkology.org> [10-06-20 15:16]:
> > >> How about putting dev-python/setuptools into
> > >> /etc/portage/package.keywords, and trying to emerge 0.6.13?
> > >
> > > I tried to re-emerge setuptools 0.6.10 and it fails the same way.
> > > So I believe (=not knowing) that this problem is caused by something
> > > outside setuptools, which gets screwed up.
> > 
> > Probably python itself, as Arttu pointed out.
> > 
> > > Problem with 0.6.13 is: If it compiles and installs itsself, 0.6.10
> > > (current version) is gone and cannot get back due to the same problem
> > > (see above). And then I have a "unstable" version, which may pull in
> > > other unstable versions of something else, which pull in....
> > 
> > Maybe, but at least in the ebuild itself there are no such dependencies.
> > If you'd need to keyword this package only, it should do no harm. If
> > more things need to be keyworded, I agree that this tends to make things
> > complicated. But at least you can quickpkg the existing version, and get
> > it back when needed without compiling with emerge -k.
> > But when 0.6.10 also fails, the problem is likely to be somewhere else.
> > 
> > > This way I have corrupted my last installed gentoo system...
> > 
> > I'm at ~amd64 now, and things are easier now :) At least for me.
> > 
> > If you are desperate: Maybe removing setuptools would at least make
> > python-updater run through, unless something would pull it in again.
> > Emerge -k setuptools back. You may be missing stuff for python 3.1, but
> > maybe this does not harm too much.
> > 
> > And report a bug at bugs.gentoo.org, so the maintainers know what's
> > going on.
> 
> I'd have another go but after setting MAKEOPTS="-j1" (although I have to admit 
> the error you posted does not look like this would make any difference).
> -- 
> Regards,
> Mick

Hi Mick,

thanks for your posting!

I set it to -j 1 and setuptools fails as before...

Best regards,
mcc

[gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[walt]

On 06/19/2010 07:55 AM, meino.cramer@gmx.de wrote:
> walt<w41ter@gmail.com>  [10-06-19 16:48]:
>> On 06/19/2010 12:37 AM, meino.cramer@gmx.de wrote:
>>>
>>> Hi,
>>>
>>> compilation of setuptools-0.6.12 aborts woth:
>>> 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>
>>
>> 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.

Just for fun, try re-emerging app-admin/eselect-python and use it to
select python3 and then go back to python2 again.

This is just guesswork.  I'm not sure if the installer for setuptools is
actually using the right version of refactor.py.  Maybe it should be using
the python2 version of refactor?  Dunno.  Can't hurt to try it.

Re: [gentoo-user] Re: Compilation aborted for setuptools-0.6.12

[meino.cramer]

walt <w41ter@gmail.com> [10-06-20 19:12]:
> On 06/19/2010 07:55 AM, meino.cramer@gmx.de wrote:
> >walt<w41ter@gmail.com>  [10-06-19 16:48]:
> >>On 06/19/2010 12:37 AM, meino.cramer@gmx.de wrote:
> >>>
> >>>Hi,
> >>>
> >>>compilation of setuptools-0.6.12 aborts woth:
> >>>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>
> >>
> >>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.
> 
> Just for fun, try re-emerging app-admin/eselect-python and use it to
> select python3 and then go back to python2 again.
> 
> This is just guesswork.  I'm not sure if the installer for setuptools 
> is
> actually using the right version of refactor.py.  Maybe it should be 
> using
> the python2 version of refactor?  Dunno.  Can't hurt to try it.
> 
> 

Hi,

thanks for your posting! :)

I did what you suggested, but it did not change the situation in
any way.

Best regards,
mcc