Hi! David Coe wrote:
> I'd like though to establish whether #include_next works in your own > build environment. Well, if you refuse to believe me... $ cd dvbcut $ echo '#include <stdlib.h>' | gcc -E - # 1 "<stdin>" # 1 "<built-in>" # 1 "<command line>" # 1 "<stdin>" # 1 "c:/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/stdlib.h" [...] $ echo '#include <stdlib.h>' | gcc -E -I import - # 1 "<stdin>" # 1 "<built-in>" # 1 "<command line>" # 1 "<stdin>" # 1 "import/stdlib.h" 1 # 1 "c:/mingw/bin/../lib/gcc/mingw32/3.4.2/../../../../include/stdlib.h" [...] As you can see, gcc loads MinGW's <stdlib.h> (after import/stdlib.h if the import directory is prepended to the search path and #include_next is used - second case). > If it does, I'll wrestle with my own MinGW/MSYS; if > it doesn't, it might be better to regress to #include "/mingw/include/" > which does accomodate a standard MinGW on an arbitrary hard drive. I suppose your MinGW installation is not as "standard" as you think. -- Michael "Tired" Riepe <mich...@mr511.de> X-Tired: Each morning I get up I die a little ------------------------------------------------------------------------------ _______________________________________________ DVBCUT-user mailing list DVBCUT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dvbcut-user