Florian Weimer
48c3c12389
Linux: Fix __glibc_has_include use for <sys/stat.h> and statx ...
The identifier linux is used as a predefined macro, so the actually
used path is 1/stat.h or 1/stat64.h. Using the quote-based version
triggers a file lookup for /usr/include/bits/linux/stat.h (or whatever
directory is used to store bits/statx.h), but since bits/ is pretty
much reserved by glibc, this appears to be acceptable.
This is related to GCC PR 80005: incorrect macro expansion of the
argument of __has_include.
Suggested by Zack Weinberg.
Reviewed-by: Carlos O'Donell <carlos@redhat.com>
2019-06-14 16:28:41 +02:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-05-23 13:20:48 +00:00
2019-06-13 16:08:20 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-02-02 14:15:27 +01:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2018-09-25 16:48:15 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2017-05-20 19:04:43 -04:00
2017-05-20 19:04:43 -04:00
2019-01-01 00:11:28 +00:00
2019-05-14 22:55:51 +02:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-06-14 16:28:41 +02:00
2019-01-01 00:11:28 +00:00
2012-05-22 13:46:29 -07:00
2019-01-03 09:32:12 -02:00
2019-01-03 09:32:12 -02:00
2019-01-03 09:32:12 -02:00
2019-01-03 09:32:12 -02:00
2019-01-03 09:32:12 -02:00
2019-01-03 09:32:12 -02:00
2019-01-03 09:32:12 -02:00
2019-01-03 09:32:12 -02:00
2019-01-03 09:32:12 -02:00
2019-01-03 09:32:12 -02:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-02-26 15:01:50 +00:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
2019-06-07 09:27:01 +02:00
2019-01-01 00:11:28 +00:00
2019-01-01 00:11:28 +00:00
48c3c12389