You think you're done at 100%...

[LB]

But then this happens:
http://i.imgur.com/IM9pN98.png

http://sourceforge.net/p/mingw/bugs/2024/

I have had to fix some problems with LLVM/Clang files, but having to fix MinGW headers is disconcerting. Well, at least it's finally built...but I'm still not done even after building it...

[Dy7SLyTq]

wow man that sucks

[LB]

It wasn't a tough fix but yeah I've spent a long time getting this to build only to discover that it doesn't actually work properly.

[naraku9333]

Are you sure it's a MinGW bug? Your example

#include <unistd.h> 
int main() {}

compiles fine for me with MinGW 4.8.1

[Dy7SLyTq]

off topic: your name is nick too? hi five

[LB]

naraku9333 wrote:

Are you sure it's a MinGW bug?

Seeing as I linked to the bug report, yes, it is. If you already read the bug report, you misread it.

@DTSCode: No, my name is Nicholas, not Nick. I hate it when people call me Nick. ;p

[Dy7SLyTq]

D: i didnt want to hi five you anyways

[keskiverto]

Saint Nicholas and Old Nick ...


When one is as apt to make their own mistakes as the C++ users are, finding the toolchain fallible is indeed scary. Oh, wait,

GCC 4.8 changes:
GCC now uses C++ as its implementation language.

On the other hand, being able to make a difference is quite satisfying.