The 01 November 2007 build will NOT be out.

[Biplab]

I am getting this on my real windows XP machine. When using MinGW GCC, but TDM build works right.

I think the version info format is the issue.

gcc version 4.2.2 (TDM-1)
gcc version 4.2.1-sjlj (mingw32-2)

This works well in my PC. I used gcc --version at command prompt it returns -

gcc (GCC) 4.2.1-dw2 (mingw32 dw2-unwind)

Then I started C::B and checking the version string by running the following script at script console.

Code Select Expand

ShowInfo(GetCompilerFactory().GetCompilerVersionString(_T("gcc")));

And it returns 4.2.1 and in my case a wx project works well with 3.4.x or 4.2.x compilers.

[stahta01]

I get a different version message for the dw2 without "dw2-unwind" in it. Did you download it from http://sourceforge.net/projects/mingw/ or somewhere else?

Tim S

Code Select Expand

gcc-dw2.exe (GCC) 4.2.1-dw2 (mingw32-2)


The popup window works for TDM GCC and not for the MinGW dw2 of sjlj ones.
Re-downloading the MinGW GCC files, I have no idea if I am using the newest file of not.
(2007-08-14 07:07) looks like the newest dw2 files.
The files seem the same and produces a blank popup.

[Biplab]

I get a different version message for the dw2 without "dw2-unwind" in it. Did you download it from http://sourceforge.net/projects/mingw/ or somewhere else?

Tim S

Code Select Expand

gcc-dw2.exe (GCC) 4.2.1-dw2 (mingw32-2)


The popup window works for TDM GCC and not for the MinGW dw2 of sjlj ones.
Re-downloading the MinGW GCC files, I have no idea if I am using the newest file of not.
(2007-08-14 07:07) looks like the newest dw2 files.
The files seem the same and produces a blank popup.

I guess I'm using the first release. But that shouldn't matter. In all cases the version check is done at C::B start-up. Thus if the pop-up is empty or malformed then the Regex has failed to parse the output.

I'll try it with the latest mingw snapshot one.

[Biplab]

It still works fine.

This is the output at command line.

gcc (GCC) 4.2.1-dw2 (mingw32-2)

And running the script correctly shows 4.2.1. Are you using self-compiled C::B or official nightly? I'm using Official nightly.

[stahta01]

It still works fine.

This is the output at command line.

gcc (GCC) 4.2.1-dw2 (mingw32-2)

And running the script correctly shows 4.2.1. Are you using self-compiled C::B or official nightly? I'm using Official nightly.

Self Compiled, which nightly are you using? I will try the latest one.

Still have the problem with Nightly download of SVN 4564, what are you using in C::B settings of
ToolChain executable - Program File - C Compiler
I have tried more than one value and none of the worked for getting anything other than blank.

Tim S

[killerbot]

I use the same files. On my PC it works. I copied the entire MinGW directory to my laptop (both are located at C:\MinGW) and both systems have C:\MinGW\bin added to PATH.

PC works ok, laptop fails [and related or not ?? on the laptop I can't debug].

Only difference : the PC was being svn updated and builded for a long time [so it still uses the old MinGW detection], the laptop was brand new install.

Note : both systems are running in a virtual machine by using VirtualBox, both Windows XP, and on the PC the host system is openSuse 10.2 , where on the laptop it is openSUSE 10.3.

[killerbot]

PC and laptop give me :

Code Select Expand


gcc (GCC) 4.2.1-dw2 (mingw32-2)

or

mingw32-gcc (GCC) 4.2.1-dw2 (mingw32-2)


Note : there have been 2 releases of 4.2.1 dw2, the very first ones, had some issues. I guess I have the second one, but as said i use the same files on both systems.

Running the script in the script console :

PC : 4.2.1
Laptop : empty string

[killerbot]

alright I have found the cause of our first problem.

Indeed, it is what I suspected. CB doesn't detect GCC correctly anymore. I already suspected this yesterday, and more precise I didn't trust the masterpath anymore. CB had detected C:\MinGW\bin instead of C:\MinGW.
Remove the \bin, and it will work OK.
I do remember some code will check to see if we are already in the bin dir, but apparently not the version checking.

Now checking if debugging works.

[EDIT] : debugging still fails on the laptop, but works on the PC :-(

[EDIT2] : fixed the debugging issue too : laptop was back on GDB 6.3, when upgrading to 6.6, it seems to work [very basic test on a Hello world console app].

[killerbot]

in comparing the 2 default.conf's I noted another difference. Debugger settings : Auto-build project to ensure-up-to-date. Both systems have this checked.

PC - default.conf : no sign of it
LAPTOP - default.conf : <AUTO_BUILD bool="1" />

[stahta01]

Verify that you have mingw32-gcc.exe in the bin folder in both the working and the non working one.
I just did a few changes and adding mingw32-gcc.exe to the non working one was one of them and it appears to have worked.

Note, You are required to re-start C::B for this work around to work.

Tim S

[killerbot]

yes it is in the bin dir. As said, both directories were/are equal :since I copied MinGW dir from the PC to the laptop.
The only difference I found was the masterpath of GCC in CB (default.conf), so it seems the latest CB detects it otherwise then before.