Eli Zaretskii: > Doesn't -std=c++11 request strict ANSI C++? _fileno is > non-ANSI, and thus isn't visible in a strict-ANSI > compilation. I suggest to try the option -std=gnu++11 > instead. But you are right -- why should one expect a non-standard function or macro in a standard header if MinGW is not obliged to implement POSIX? On the other hand, this worked with GCC 4.*... Since the project I am trying to build and contribute to is configured not to use the GNU extensions, I have to find another way of acessing fileno/_fileno. May I link it in manually from the MinGW library in which it *is* implemented? Or may I, perhaps, ask to to implement fileno as a favour?
Fork