View previous topic :: View next topic |
Author |
Message |
davidshen84 Guru
Joined: 09 Aug 2008 Posts: 314
|
Posted: Mon Jun 20, 2016 12:49 pm Post subject: How to interpret >=dev-libs/boost-1.52.0-r6:0/1.60.0= ? |
|
|
I got some conflicts when emerge world. And I don't quite get what the error message means.
Quote: | dev-libs/boost:0
(dev-libs/boost-1.61.0:0/1.61.0::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot)
(dev-libs/boost-1.60.0:0/1.60.0::gentoo, installed) pulled in by
>=dev-libs/boost-1.52.0-r6:0/1.60.0=[python,python_targets_python2_7(-),-python_single_target_python2_7(-)] required by (media-libs/vigra-1.10.0:0/0::gentoo, installed)
^^^^^^^^^^
(and 5 more with the same problem) |
Please help me understand the line with ">=dev-libs/boost-1.52.0-r6:0/1.60.0=".
Thanks~ _________________ David Shen |
|
Back to top |
|
|
Roman_Gruber Advocate
Joined: 03 Oct 2006 Posts: 3846 Location: Austro Bavaria
|
Posted: Wed Jun 29, 2016 10:18 pm Post subject: |
|
|
Quote: | python_targets_python2_7(-),-python_single_target_python2_7(-) |
Check your
python
and python single targets
e.g. Example of my box. I have python 2.7 and 3.5 enabled on a generic basis. and the single target set to python 3.5
Code: | grep PYTHON /etc/make.conf
PYTHON_TARGETS="python2_7 python3_5"
PYTHON_SINGLE_TARGET="python3_5"
|
of course you can change it on a package basis too
Code: | ASUS-G75VW ~ # grep python_ /etc/portage/package.use
app-text/asciidoc python_single_target_python2_7
|
That bugger needs 2.7 python single target for example
---
Without a knowledge of your box. What you want and such i gave you a generic hint.
Choose those pyhton targets according to your needs and the stuff should be fixed.
You can choose it on a package basis too when needed, as i have for asciidoc |
|
Back to top |
|
|
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
Posted: Thu Jun 30, 2016 4:21 am Post subject: Re: How to interpret >=dev-libs/boost-1.52.0-r6:0/1.60.0= |
|
|
davidshen84 wrote: | Please help me understand the line with ">=dev-libs/boost-1.52.0-r6:0/1.60.0=". |
It's simple, once you know how. This here:
Quote: | Code: | (dev-libs/boost-1.60.0:0/1.60.0::gentoo, installed) pulled in by
>=dev-libs/boost-1.52.0-r6:0/1.60.0=[python,python_targets_python2_7(-),-python_single_target_python2_7(-)] required by (media-libs/vigra-1.10.0:0/0::gentoo, installed) |
|
means the boost-1.60.0 you have installed is currently a dependency media-libs/vigra needs (boost-1.52.0-r6 or newer).
This:
Quote: | Code: | (dev-libs/boost-1.61.0:0/1.61.0::gentoo, ebuild scheduled for merge) pulled in by
(no parents that aren't satisfied by other packages in this slot) |
|
means something else wants to install boost-1.61.0. The slot is 0 on both, which means they're compatible with each other but can't be installed in parallel. They have different subslots, which means if you update boost (what portage wants to do here) anything built against it needs recompiling.
And finally, portage won't risk rebuilding media-libs/vigra on its own because you haven't asked it to, the most likely reason is that it's not a @world package and you haven't said --with-bdeps=y. That one switch is all you really need to add in most cases like this. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|