19.07.2018 00:10 Sandro Mani <manisan...@gmail.com> wrote:
> 
>  Hi
> 
>  I'm hitting the following with qt5-qtbase:
> 
>  /usr/include/linux/stat.h:56:8: error: redefinition of 'struct
> statx_timestamp'
>   struct statx_timestamp {
>          ^~~~~~~~~~~~~~~
>  In file included from /usr/include/sys/stat.h:446,
>                   from
> /builddir/build/BUILD/qtbase-everywhere-src-5.11.1/mkspecs/linux-g++/qplatformdefs.h:75,
>                   from
> /builddir/build/BUILD/qtbase-everywhere-src-5.11.1/src/corelib/io/qfilesystemengine_unix.cpp:42:
>  /usr/include/bits/statx.h:25:8: note: previous definition of 'struct
> statx_timestamp'
>   struct statx_timestamp
>          ^~~~~~~~~~~~~~~
> 
> 
>  I.e. struct statx_timestamp in linux/stat.h (included directly by
> qfilesystemengine_unix.cpp) is conflicting with struct statx_timestamp in
> bits/statx.h included via sys/stat.h.
> 
>  This has begun with glibc-2.27.9000.
> 
>  Any ideas?

True, this change has been introduced with the upstream commit 93304f5 [1]
and has reached Fedora Rawhide since glibc-2.27.9000-38. [2]
Maybe /usr/include/linux/stat.h requires some conditional #ifdef including
the relevant part only if GLIBC < 2.28. But that's part of kernel, should
be reported and fixed upstream.

I think that Florian who is also active in this list should speak. For now
the simplest workaround for you is to downgrade glibc to something just few
days older.

Regards,

Rafal


[1] https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=93304f5
[2]
https://src.fedoraproject.org/rpms/glibc/c/6404b258962769f7c4d1108c52aece4b314ee27f?branch=master
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WIIFDJYB5N4HA7CLWH7M4KRZOAOWZVF6/

Reply via email to