1 |
On 06/25 12:33, Nikos Chantziaras wrote: |
2 |
> On 25/06/18 09:37, Arve Barsnes wrote: |
3 |
> > On 25 June 2018 at 04:19, <tuxic@××××××.de> wrote: |
4 |
> > > I think, my attempt to play with words despite the fact that I am no |
5 |
> > > native speaker ;) has spent some confusion (or I understand something |
6 |
> > > wrong right now: |
7 |
> > > |
8 |
> > > In my make,conf this is set |
9 |
> > > |
10 |
> > > ACCEPT_KEYWORDS="~amd64" |
11 |
> > > |
12 |
> > > so I am on unstable. |
13 |
> > |
14 |
> > The actual error, in case anyone knows the fix: |
15 |
> > |
16 |
> > /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: |
17 |
> > fatal error: sys/ustat.h: No such file or directory |
18 |
> > #include <sys/ustat.h> |
19 |
> > |
20 |
> > So maybe rebuild glibc or something? |
21 |
> |
22 |
> Is the file there? It's "/usr/include/sys/ustat.h" and qfile says it's from |
23 |
> glibc: |
24 |
> |
25 |
> $ qfile /usr/include/sys/ustat.h |
26 |
> sys-libs/glibc (/usr/include/sys/ustat.h) |
27 |
> |
28 |
> I'm on glibc-2.27-r4. |
29 |
> |
30 |
> If you can't get rid of the error, it might be worth trying disabling the |
31 |
> "sanitize" USE of gcc. |
32 |
> |
33 |
> |
34 |
|
35 |
Hi Nikos, |
36 |
|
37 |
I am on glibc-9999(2.2) and the qfile command does not find that file. |
38 |
Before switching off the sanitizer...for it is used? |
39 |
Not that I replace one visible error with a non visible random error, |
40 |
which is even harder to trace down... |
41 |
|
42 |
Cheers |
43 |
Meino |