On 2 February 2016 at 07:54, Jakub Jelinek wrote:
>
> That said, why does it bother to do such a mess? Does it think the g++
> driver is not able to do that itself?
>
I am not sure why qmake-qt5 doesn't want to trust gcc for the system
include dirs, but well.. it doesn't.
I reduced the problem down to this. Consider the following program:
#include <algorithm>
int main(){}
This compiles fine with both gcc5 and 6 with
g++ -c inctest.cpp -o inctest.o
On the other hand, it compiles fine with gcc5, but fails with gcc6 if
the compiler is invoked liked this:
g++ -c -isystem /usr/include inctest.cpp -o inctest.o
The failure message is
/usr/include/c++/6.0.0/cstdlib:75:25: fatal error: stdlib.h: No such
file or directory
I am not sure what is the expected behavior. Maybe people familiar
with gcc can shed some light.
I noticed the difference: In cstdlib, the gcc5 line 75
#include <stdlib.h>
became in gcc6:
#include_next <stdlib.h>
Thanks,
Orcan
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
