View previous topic :: View next topic |
Author |
Message |
Thistled Guru
Joined: 06 Jan 2011 Posts: 572 Location: Scotland
|
Posted: Sat Sep 07, 2013 4:14 pm Post subject: |
|
|
With your suggestion of python-2.7 site packages, would that mean Python-2.7 is the preferred version?
I think some packages may still not be happy with the Python-3* series. Is that still the case?
I am currently at 3.2 and was thinking it might be best to switch back to 2.7. _________________ Whatever you do, do it properly! |
|
Back to top |
|
|
floppymaster Developer
Joined: 07 Jul 2010 Posts: 229 Location: Detroit, MI, USA
|
Posted: Sat Sep 07, 2013 4:37 pm Post subject: |
|
|
I just saw python2.7 in your log output in previous posts.
"emerge /usr/lib/python2.7/site-packages" tells emerge to reinstall any packages that have installed any files in that directory.
It really doesn't have anything to do with what version of python you have eselected. |
|
Back to top |
|
|
Thistled Guru
Joined: 06 Jan 2011 Posts: 572 Location: Scotland
|
Posted: Sat Sep 07, 2013 4:47 pm Post subject: |
|
|
Yesterday, or it may have been the day before, I ran into trouble with some packages failing to build.
They all had the same error that I was experiencing when calling java-config.
I thought the reason why some of these packages were failing was because I had python set to 2.7.
So, I changed python to 3.2 and ran python-updater.
Obviously the packages still failed.
So now it seems it had something to do with python and not java.
As I type this python-updater is rebuilding a handful of packages, one of which is Virtualbox.
Virtualbox would always fail within the first few seconds of compile time because the ebuild
Quote: | couldn't determine a VM |
but so far Virtualbox is building, so it seems I may have overcome this hurdle.
When Virtualbox is finished, I will attempt to build the packages which were failing with the gdbus-codegen errors.
Then I will take it from there.
I do hope this means I can buy floppymaster and TomWij a beer.
Fingers crossed.
Peace. _________________ Whatever you do, do it properly! |
|
Back to top |
|
|
Thistled Guru
Joined: 06 Jan 2011 Posts: 572 Location: Scotland
|
Posted: Sat Sep 07, 2013 4:58 pm Post subject: |
|
|
** UPDATE **
Ok, Virtualbox failed, but that is okay, because I recognise from the output I need to rebuild ( or is just build. lol)
xjavac.
I was told to build xjavac when I ran java-check-environment.
Again, I couldn't build the packages because ebuilds couldn't find a VM.
I think they are now, so this should be good to know.
I will know in the next hour.
So floppymaster, is it still a good idea for me to emerge python-2.7/site-packages anyway?
Like you say, although I have eselected python-3.2 it is safe to emerge python-2.7/site-packages ? _________________ Whatever you do, do it properly! |
|
Back to top |
|
|
Thistled Guru
Joined: 06 Jan 2011 Posts: 572 Location: Scotland
|
Posted: Sun Sep 08, 2013 1:39 pm Post subject: |
|
|
Seems this is now fixed for me.
The build errors have gone. Now I am just rebuilding lots of packages that depend on Python.
I have made the transition to 3.2
A very big thanks to TomWij floppymaster and Donahue for your contributions and solution. _________________ Whatever you do, do it properly! |
|
Back to top |
|
|
figofuture n00b
Joined: 10 Apr 2011 Posts: 3 Location: china
|
Posted: Wed Sep 25, 2013 7:42 am Post subject: |
|
|
I also have the same java-config issue, after I reinstalled python-exec, it is resolved. Thanks! |
|
Back to top |
|
|
|