Re: Behavior of fixincludes when using --with-advance-toolchain

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2020-02-03 10:57 -0300, Matheus Castanho wrote:
> GCC build is failing due to an undefined macro (__glibc_has_include)
> used by a system header (bits/statx.h). This macro used to be defined by
> sys/cdefs.h. Both headers come from glibc, but that specific macro got
> removed recently (glibc commit bfa864e1645e).
> 
> During the fixincludes step, GCC is processing headers from /usr/include
> only. In this process, it 'fixes' bits/statx.h from that tree, which
> corresponds to an older version of glibc installed on the system (which
> uses the macro). This fixed header seems to take precedence over other
> versions of the same header the compiler may find (for example, under
> <custom-dir>).

"Fixing" bits/statx.h is a known bug (PR91085).  It actually breaks this
header :(.

I'm not familiar with --with-advance-toolchain, though.
-- 
Xi Ruoyao <xry111@xxxxxxxxxxxxxxxx>
School of Aerospace Science and Technology, Xidian University




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux