| 1 |
On 25/06/18 09:37, Arve Barsnes wrote: |
| 2 |
> On 25 June 2018 at 04:19, <tuxic@××××××.de> wrote: |
| 3 |
>> I think, my attempt to play with words despite the fact that I am no |
| 4 |
>> native speaker ;) has spent some confusion (or I understand something |
| 5 |
>> wrong right now: |
| 6 |
>> |
| 7 |
>> In my make,conf this is set |
| 8 |
>> |
| 9 |
>> ACCEPT_KEYWORDS="~amd64" |
| 10 |
>> |
| 11 |
>> so I am on unstable. |
| 12 |
> |
| 13 |
> The actual error, in case anyone knows the fix: |
| 14 |
> |
| 15 |
> /var/tmp/portage/sys-devel/gcc-7.3.0-r3/work/gcc-7.3.0/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:157:10: |
| 16 |
> fatal error: sys/ustat.h: No such file or directory |
| 17 |
> #include <sys/ustat.h> |
| 18 |
> |
| 19 |
> So maybe rebuild glibc or something? |
| 20 |
|
| 21 |
Is the file there? It's "/usr/include/sys/ustat.h" and qfile says it's |
| 22 |
from glibc: |
| 23 |
|
| 24 |
$ qfile /usr/include/sys/ustat.h |
| 25 |
sys-libs/glibc (/usr/include/sys/ustat.h) |
| 26 |
|
| 27 |
I'm on glibc-2.27-r4. |
| 28 |
|
| 29 |
If you can't get rid of the error, it might be worth trying disabling |
| 30 |
the "sanitize" USE of gcc. |
Archives