User forums > Nightly builds
The 19 October 2007 build (4545) is out.
rafael:
--- Quote from: killerbot on October 19, 2007, 08:21:37 pm ---
* wxSmith: Fixed bug when generating event handler by double-clicking on item
--- End quote ---
Just wanted to say thank you very much, that bug was really annoying! :P
Rye:
Does anybody plan on fixing the 'forced rebuild on compile' bug anytime soon as it is really starting to piss me off :(.
three_minute_hero:
--- Quote from: jens on October 21, 2007, 06:15:50 pm ---We have the same versions of libs codeblocks uses, inspite of one: I have also "libxcb1" and "libxcb-xlib0" installed. But I don't think that makes a difference.
You can of course install them and see if this makes a difference.
By the way you should replace "lenny" with "unstable" for my repo, even if both versions work (for me) or have errors (for you).
At the moment I don't have any idea what's wrong with your install.
As workaround you can use codeblocks without glibc's extra tests.
--- End quote ---
No problem. I'll notify if something changes.
Thanks!
TDragon:
--- Quote from: Rye on October 22, 2007, 07:23:18 am ---Does anybody plan on fixing the 'forced rebuild on compile' bug anytime soon as it is really starting to piss me off :(.
--- End quote ---
As far as I'm aware, none of the developers are able to reproduce the problem; this makes fixing the bug much harder. Has an informative, detailed bug report been filed?
ASJ:
--- Quote from: TDragon on October 22, 2007, 02:48:43 pm ---
--- Quote from: Rye on October 22, 2007, 07:23:18 am ---Does anybody plan on fixing the 'forced rebuild on compile' bug anytime soon as it is really starting to piss me off :(.
--- End quote ---
As far as I'm aware, none of the developers are able to reproduce the problem; this makes fixing the bug much harder. Has an informative, detailed bug report been filed?
--- End quote ---
I do not know about a detailed bug report, but I 'm not sure how to exactly file one because effectively nothing is crashing, only some unexpected behavior occurs. In my situation, the problems started after I upgraded my openSUSE 10.2 machine to openSUSE 10.3.
Could it be that the problems are related to this upgrade (several libraries and gcc have been upgraded to newer versions)? If none of the developers are using openSUSE 10.3 this could maybe explain things......
I did notice at least an upgrade of gcc to 4.2.1. Probably many more libraries are updated but currently I do not have access to a 10.2 installation in order to compare the versions of the installed libraries :?
I did try to use the gcc 4.1.3 binaries which seem to be installed in parallel to 4.2.1. Using these with the builds of luneo7 did however not make any difference at all (maybe because he used gcc 4.2.1 to build it???, just a wild guess) and the following things happen:
- starting a debug session or performing a plain build both always results in a complete rebuild (including recompiling the precompiled header etc.)
- when the debugger is started (according to the messages in "the debugger window") the dialog window saying: "The 'Code::Blocks default' has changed. Do you want to save it? " appears, even though the Debug build target is used.
I know that this is a bad "bug report", but I just tried to describe things a bit more elaborately.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version