On 06/25 12:33, Nikos Chantziaras wrote:
> On 25/06/18 09:37, Arve Barsnes wrote:
> > On 25 June 2018 at 04:19,  <[email protected]> wrote:
> > > I think, my attempt to play with words despite the fact that I am no
> > > native speaker ;) has spent some confusion (or I understand something
> > > wrong right now:
> > > 
> > > In my make,conf this is set
> > > 
> > > ACCEPT_KEYWORDS="~amd64"
> > > 
> > > so I am on unstable.
> > 
> > The actual error, in case anyone knows the fix:
> > 
> > /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:
> > fatal error:  sys/ustat.h: No such file or directory
> >   #include  <sys/ustat.h>
> > 
> > So maybe rebuild glibc or something?
> 
> Is the file there? It's "/usr/include/sys/ustat.h" and qfile says it's from
> glibc:
> 
>   $ qfile /usr/include/sys/ustat.h
>   sys-libs/glibc (/usr/include/sys/ustat.h)
> 
> I'm on glibc-2.27-r4.
> 
> If you can't get rid of the error, it might be worth trying disabling the
> "sanitize" USE of gcc.
> 
> 

Hi Nikos,

I am on glibc-9999(2.2) and the qfile command does not find that file.
Before switching off the sanitizer...for it is used?
Not that I replace one visible error with a non visible random error,
which is even harder to trace down...

Cheers
Meino



Reply via email to