2 ms·
If include <version> in angle brackets finds some Autoconf VERSION detritus, it's because the compiler has been wrongly told to look for <...> headers locally.
by kazinator 7y ago
If include <version> in angle brackets finds some Autoconf VERSION detritus, it's because the compiler has been wrongly told to look for <...> headers locally. (Probably by the same Autoconf junk.)
There is a (not so) modern (any more) gcc option -iquote to specify a directory to search for #include "..." without affecting #include <...>.
In the TXR project I have a "signal.h" local file:
http://www.kylheku.com/cgit/txr/tree/signal.h http://www.kylheku.com/cgit/txr/tree/signal.h
Yet, <signal.h> is also included. Like in this file:
http://www.kylheku.com/cgit/txr/tree/signal.c http://www.kylheku.com/cgit/txr/tree/signal.c
which has both #include <signal.h> and #include "signal.h".
This is fine, if you know what you're doing. #include <signal.h> has no business finding that local file, and will not do so, unless someone screws up.