User forums > Help
WIndows Project Moved to Linux = Errors
Morphius Faydal:
--- Quote from: TDragon on June 16, 2007, 05:10:52 am ---
--- Quote from: MorphiusFaydal on June 16, 2007, 05:07:13 am ---Also, running touch on all the files should modify the timestamp, so you could, hopefully, work around this GCC bug.
--- End quote ---
Actually, the bug is in the fact that GCC produces incorrect output when compiling C::B -- the error occurs when C::B itself tries to read a file's timestamp and, because of the incorrect output, fails. Because it can't read the timestamp, it assumes the file doesn't exist and skips compiling it -- then errors out because it can't find the compiled object file.
--- End quote ---
Ah... I've never encountered said bug, and I guess I didn't read the bug report right. My apologies.
arew264:
Okay, that does appear to be the problem, and I am recompiling, which takes somewhere near 15 minutes, even on my awesome 3GHz Pentium 4 with hyperthreading, a gig of ram, and pure awesome (except the ECS mobo - NEVER going to TOUCH one of those again)
arew264:
Well, I set that -fno-strict-aliasing flag, recompiled, and w00t, my project is running under linux. Thank you!
TDragon:
You're welcome!
A note to the C::B devs:
The compiler depslib hash table functionality is not a pretty piece of work. I'm not sure how standards-conformant it is to pun a pointer between two types of structs with different members, but my guess is "not very". Even if nothing else, it's breaking strict-aliasing rules, so in my (not so) professional opinion, it should be rewritten or the compiler depslib replaced.
A note to the world in general:
My 500th post, heh.
Morphius Faydal:
--- Quote from: TDragon on June 16, 2007, 08:57:14 pm ---You're welcome!
A note to the C::B devs:
The compiler depslib hash table functionality is not a pretty piece of work. I'm not sure how standards-conformant it is to pun a pointer between two types of structs with different members, but my guess is "not very". Even if nothing else, it's breaking strict-aliasing rules, so in my (not so) professional opinion, it should be rewritten or the compiler depslib replaced.
A note to the world in general:
My 500th post, heh.
--- End quote ---
How hard would it be to recode the relevant sections to be more standards compliant?
And wow. You've been around a lot. :-P
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version