| 1 |
> |
| 2 |
> > I would do something like 'emerge -1 xorg-server xorg-drivers |
| 3 |
> > @x11-module-rebuild mesa llvm clang' then restart X and try again. |
| 4 |
> |
| 5 |
> Thank you for your reply. |
| 6 |
> |
| 7 |
> Initially, I understood the above recomendation as the suggestion to |
| 8 |
> rebuild the packages mentioned above with different use flags. |
| 9 |
> |
| 10 |
> Do you think that rebuilding them with the same use flags may help? |
| 11 |
> |
| 12 |
|
| 13 |
It can, for example, if the major version of the kernel has changed but you |
| 14 |
havent rebuild xorg since (I only recall having this issue once). |
| 15 |
|
| 16 |
If you use newuse and changed-deps with emerge its probably less likely to |
| 17 |
find other issues. |
| 18 |
|
| 19 |
|
| 20 |
> The said problem appeared just since the intallation of the new |
| 21 |
> Gentoo system in January-February 2018 and not since changing |
| 22 |
> the major version of gcc this spring. |
| 23 |
> |
| 24 |
> P.S. clang is not installed on my Gentoo system at all. |
| 25 |
> |
| 26 |
> |
| 27 |
I've checked the dependencies on my system, and firefox is pulling that in |
| 28 |
for me, but checking the ebuilds you can see it becomes a dependency from |
| 29 |
v60 onwards; |
| 30 |
|
| 31 |
/usr/portage/www-client/firefox $ ls |
| 32 |
files/ firefox-52.9.0.ebuild Manifest |
| 33 |
firefox-52.6.0.ebuild firefox-60.1.0.ebuild metadata.xml |
| 34 |
firefox-52.8.0.ebuild firefox-61.0-r1.ebuild |
| 35 |
/usr/portage/www-client/firefox $ grep clang * |
| 36 |
grep: files: Is a directory |
| 37 |
firefox-60.1.0.ebuild: >=sys-devel/clang-4.0.1 |
| 38 |
firefox-60.1.0.ebuild: has_version "sys-devel/clang:${LLVM_SLOT}" |
| 39 |
firefox-61.0-r1.ebuild: >=sys-devel/clang-4.0.1 |
| 40 |
firefox-61.0-r1.ebuild: has_version "sys-devel/clang:${LLVM_SLOT}" |
| 41 |
/usr/portage/www-client/firefox $ |
Archives