Okay, this was a good one. You know the feeling when you're compiling code, and the compiler spits out some ridiculous error message, and you look at the code and you look and you look and you KNOW that it's right. It MUST be a bug in the compiler...right? I mean, maybe? Just this once?
Or maybe it's your filesystem! I'm building a large code tree on an embedded system, where I'm running the OS and local storage off a micro-SD card, and damned if I'm not seeing non-deterministic build results. I'll get a compile errors like "`unsignet’ undeclared", check the code, and find that it actually does say "unsigned" -- it slipped a bit while reading the source. Then I'll run "make" again, and it'll get a few files further down, then die with "stray '\3' in program". Doesn't really instill confidence in the hardware...
No comments:
Post a Comment