Closed Petross404 closed 5 years ago
What is the problem you actually have with capstone 4? From the links I couldn't understand what it is.
My bad. There is something missing from my ebuild so when capstone was installed with a different soname, edb preserved the old capstone.so.3
instead of getting rebuilt with capstone.so.4
and portage deleting the old one.
The FEATURES=preserve-libs setting will cause Portage to preserve libraries when sonames change during upgrade or downgrade, only as necessary to satisfy shared library dependencies of installed consumers. Preserved libraries are automatically removed when there are no remaining consumers, which occurs when consumer packages are rebuilt or uninstalled. Ideally, rebuilds are triggered automatically during updates, in order to satisfy slot-operator dependencies. Before emerge exits after installing updates, if there are remaining preserved libraries because slot-operator dependencies have not been used to trigger automatic rebuilds, then emerge will display a message like the following:
More details here.
Thanks.
Here it is mentioned that edb needs
capstone >=3
, but at bug 673466 one can see thatdev-libs/capstone-4.0
(i.e >=3) creates a problem.Is capstone-4 incompatible with edb?
Thanks.