We are pleased to announce the release of Dev-C++ 4.9.9.2.
This is mainly a bug-fix release that should correct many known problems.
It also include latest Mingw with GCC 3.4.2.
Darn, I hope so. A large fraction of the issues that I see on this board are due to people either installing Dev, or their projects in directories with spaces in theim. That is why the firs thing that I say in the FAQ thread relates that "SPACES ARE BAD". :)
Wayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
install program just shields you from problems mingw has with spaces. dev-c++ doesn't have any problems with spaces, but then people ask the questions, that are really mingw related, here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have not seen it in the pre-release stuff I have worked with. What exactly do you mean by "can't link"? Can you post a full, representative example of the compile log for something that fails to link please?
Wayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Found the error. By some reason under 'Project Options/Compiler/Linker' "Do not use standard system startup files or libraries" changed to Yes from No when switching to 4.9.9.2. If this is not a bug I must have done this in my sleep because I have no memory of doing this?!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Humm, yes...
There's something odd when loading an old project.
Optimization settings are different.
And I also get some linker errors; I'm investigating
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
please note that gcc has change - this is a big step, but 3.4.2 has been reported to be stable, so we went with latest stable. There definitely are some incompatibilites. Some options reported in 3.3.1 as deprecated, but gave only warnings, in 3.4.2 give errors.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, I think I've found it with carefully checking my project settings.
There definitely is an incompatibility of 4.9.9.2 with the project files of 4.9.9.1.
4.9.9.2 thought that Profiling has been enabled in my .dev file; producing a "undefined reference to 'mcount'" linker error message. (I never so far ever activated the profiling, I'm certain)
I disabled the profiling and everything was OK again ! :-D
Note :
Strangely, I add the problem on several of my projects created with 4.9.9.1, but not all of them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does this release include the newest version of binutils? The 4991 didn't. Remember, there was a nasty (dangerous) bug in the old binutils that 4991 shipped with that showed up for users of Win9X.
If by newest you mean latest stable then yes it contains binutils 2.15.91-20040904-1
there's a newer candidate version (not stable yet), it will probably appear on devpaks.org soon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
it's a new option. you also get similar question when uninstalling.
dev-c++ when you first run it also checks the validity of paths and attempts to correct it (if you upgraded from 4.9.9.1 you couldn't miss it). so it's hard (still not impossible) to get unable to run program file message
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello !
We are pleased to announce the release of Dev-C++ 4.9.9.2.
This is mainly a bug-fix release that should correct many known problems.
It also include latest Mingw with GCC 3.4.2.
You can download it from :
http://bloodshed.net/dev/devcpp.html
As usual, you can report problems and bugs at :
http://bloodshed.net/bugs
Greetings from the Dev-C++ developers.
Ooh, nice. Downloading any second now.
Nice one Colin.
Wow, the servers are extremely slow!
Good job, can't wait to try it.
Downloading right now...
The 4.9.9.2 release seems to not allow path names with spaces. Is this intentional?
Darn, I hope so. A large fraction of the issues that I see on this board are due to people either installing Dev, or their projects in directories with spaces in theim. That is why the firs thing that I say in the FAQ thread relates that "SPACES ARE BAD". :)
Wayne
Spaces are a fact of life. The install program has to deal with them.
install program just shields you from problems mingw has with spaces. dev-c++ doesn't have any problems with spaces, but then people ask the questions, that are really mingw related, here.
4.9.9.2 can't link my old project developed in 4.9.9.1. Anyone else having the same problem?
I have not seen it in the pre-release stuff I have worked with. What exactly do you mean by "can't link"? Can you post a full, representative example of the compile log for something that fails to link please?
Wayne
4.9.9.2 default is to use 'fast but imperfect dependency generation'.
Try disabling this and select rebuild all.
/Lars.
Found the error. By some reason under 'Project Options/Compiler/Linker' "Do not use standard system startup files or libraries" changed to Yes from No when switching to 4.9.9.2. If this is not a bug I must have done this in my sleep because I have no memory of doing this?!
Some posts from early this morning seem to show some changes in project options for existing projects.
This of course does not preclude explanations such as sleepwalking or demonic possession of your computer ;)
Wayne
the only difference between 4991 and 4992 project files should be this:
http://sourceforge.net/tracker/?group_id=10639&atid=110639&func=detail&aid=1112782
I removed that option as it returned an error in 342 and was deprecated long time before 331, so it was useless anyway.
Humm, yes...
There's something odd when loading an old project.
Optimization settings are different.
And I also get some linker errors; I'm investigating
please note that gcc has change - this is a big step, but 3.4.2 has been reported to be stable, so we went with latest stable. There definitely are some incompatibilites. Some options reported in 3.3.1 as deprecated, but gave only warnings, in 3.4.2 give errors.
OK, I think I've found it with carefully checking my project settings.
There definitely is an incompatibility of 4.9.9.2 with the project files of 4.9.9.1.
4.9.9.2 thought that Profiling has been enabled in my .dev file; producing a "undefined reference to 'mcount'" linker error message. (I never so far ever activated the profiling, I'm certain)
I disabled the profiling and everything was OK again ! :-D
Note :
Strangely, I add the problem on several of my projects created with 4.9.9.1, but not all of them.
Maybe we nee to put this answer in a seperate, named thread, something like
FIX FOR LINKER ISSUES IN 4.9.9.2
??
Wayne
http://sourceforge.net/forum/forum.php?thread_id=1234994&forum_id=48211
please report if it fixed the problem
Everything works fine now.
Big thanks to developers for this release!!
Anders
Does this release include the newest version of binutils? The 4991 didn't. Remember, there was a nasty (dangerous) bug in the old binutils that 4991 shipped with that showed up for users of Win9X.
http://sourceforge.net/forum/forum.php?thread_id=1144729&forum_id=48211
RaX
If by newest you mean latest stable then yes it contains binutils 2.15.91-20040904-1
there's a newer candidate version (not stable yet), it will probably appear on devpaks.org soon
If by newest you mean latest stable then yes it contains binutils 2.15.91-20040904-1
Yep, that's great! Thanks!
RaX
I noticed in the installation, there is an option to delete old configuration files.
Is this a new option. If so, well done, it should stop 9 tenths of the problems people get.
it's a new option. you also get similar question when uninstalling.
dev-c++ when you first run it also checks the validity of paths and attempts to correct it (if you upgraded from 4.9.9.1 you couldn't miss it). so it's hard (still not impossible) to get unable to run program file message