On 01/20/14 23:23, Tamer Higazi wrote: > You were RIGHT! > > I had to comment out at make.conf 2 lines (last line wasn't enough): > > PYTHON_TARGETS and PYTHON_SINGLE_TARGET as well. > > Thank you David!
The reason this works is that the PYTHON_TARGETS are maintained in the portage profile. You will almost always need a python2 and at least one python3, and portage automatically keeps them update date. It works much like regular dependencies, things you need get pulled in so you don't have to worry about them. ebuilds with special needs about python versions declare what they needs and portage does the necessary. When you manually set these things in make.conf, you override the heavy lifting the devs already did for you and often it doesn't work out right. > > > Tamer > > On 01/20/14 21:45, David Abbott wrote: >> Try commenting them out. >> [snip] >> Regards, >> David >> > > > > -- Alan McKinnon alan.mckin...@gmail.com
