| 1 |
Hi, |
| 2 |
|
| 3 |
I started emerge -e @world |
| 4 |
|
| 5 |
and it stops with this message: |
| 6 |
|
| 7 |
The following mask changes are necessary to proceed: |
| 8 |
(see "package.unmask" in the portage(5) man page for more details) |
| 9 |
# required by @selected |
| 10 |
# required by @world (argument) |
| 11 |
# /usr/portage/profiles/releases/17.0/package.mask: |
| 12 |
# Andreas K. Huettel <dilfridge@g.o> (27 May 2017) |
| 13 |
# In the 17.0 profiles we assume that our system compiler uses C++14 |
| 14 |
# or later as default language setting. This means it has to be at |
| 15 |
# least GCC 6. If you need an older compiler for specific purposes, |
| 16 |
# feel free to unmask it, however, using it for normal emerging of |
| 17 |
# packages is neither recommended nor supported in any way. |
| 18 |
=sys-devel/gcc-5.4.0-r3 |
| 19 |
# required by @selected |
| 20 |
# required by @world (argument) |
| 21 |
# /usr/portage/profiles/releases/17.0/package.mask: |
| 22 |
# Andreas K. Huettel <dilfridge@g.o> (27 May 2017) |
| 23 |
# In the 17.0 profiles we assume that our system compiler uses C++14 |
| 24 |
# or later as default language setting. This means it has to be at |
| 25 |
# least GCC 6. If you need an older compiler for specific purposes, |
| 26 |
# feel free to unmask it, however, using it for normal emerging of |
| 27 |
# packages is neither recommended nor supported in any way. |
| 28 |
=sys-devel/gcc-4.9.4 |
| 29 |
|
| 30 |
|
| 31 |
For me it is unclear, whether I should unmask or mask these compilers. |
| 32 |
So I added them to /etc/portage/package.mask/. ,restarted the whole |
| 33 |
thing only to get the same message. |
| 34 |
|
| 35 |
So...from the logical point of view unmasking would be the correct |
| 36 |
way....but we are all urged to >gcc-6.4.0 ... so unmasking would be |
| 37 |
wrong...also from a logical point of view. |
| 38 |
|
| 39 |
Cheers |
| 40 |
Meino |
Archives