User forums > Nightly builds
The 31 May 2007 build will NOT be out.
stahta01:
--- Quote from: kingfox on June 02, 2007, 06:13:39 am ---@stahta01
Thank you. I'm not sure whether they are error or warning. Because the color of these message is red, so I think they are some error message.
The strange thing is: when I recompile C::B without clean the previous compiled output, there isn't any error! But when I run the output executable file, it crashed. I don't know why. So I cleaned all the compiled output files and try to compile it again.
BTW: I'm using mingw gcc 4.1.2 and wxwidgets 2.8.3.
--- End quote ---
FYI: I have been getting warnings messages that are red sometimes.
Tim S
kingfox:
I cleaned all the previously compiled output and recompiled C::B, and the last two sentences of build log are:
--- Quote ---Process terminated with status 0 (56 minutes, 41 seconds)
50 errors, 4744 warnings
--- End quote ---
But then I press CTRL-F9 to compile it again without clean the previously compiled output, it said:
--- Quote ---Process terminated with status 0 (0 minutes, 14 seconds)
0 errors, 0 warnings
--- End quote ---
The attachments are two build log. The first one is with error message, and the second one is the log of recompiling.
[attachment deleted by admin]
rickg22:
I just fixed the "warnings as errors" problem. See this thread. Please update your copy to the latest SVN.
Also, please update your wxWidgets to 2.8.4. wxWidgets 2.8.3 is buggy.
stahta01:
@kingfox
Try turning off compiler option -W and see if errors go away.
Second, Try to ignore errors and see if you can compile newest SVN.
Tim S
rickg22:
I noticed another thing. GCC 3.4.x has a bug regarding STL and optimizations. Many warnings of uninitialized variable inside STL sources are false positives. There's nothing we can do about it (I've tried, believe me) but GCC keeps spitting those warnings on me.
There's nothing to worry about, since that's a GCC bug and not a C::B bug.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version