dev-cpp-users

Re: [Dev-C++] Where can I get it?

[<or...@vp...>]

Guillermo Gutierrez wrote:
> After upgrading my MinGW to 3.4, I am getting the following errors tryi=
ng to compile:
> Main.cpp:1: warning: `nul.gcda' is not a gcov data file In file include=
d from W:/Dev-Cpp/include/c++/mingw32/bits/c++locale.h:43,
>                  from W:/Dev-Cpp/include/c++/iosfwd:46,
>                  from W:/Dev-Cpp/include/c++/ios:44,
>                  from W:/Dev-Cpp/include/c++/ostream:45,
>                  from W:/Dev-Cpp/include/c++/iostream:45,
>                  from Main.cpp:1:
> W:/Dev-Cpp/include/c++/cstdio:168: error: `::vfscanf' has not been decl=
ared=20
> W:/Dev-Cpp/include/c++/cstdio:169: error: `::vscanf' has not been decla=
red=20
> W:/Dev-Cpp/include/c++/cstdio:171: error: `::vsscanf' has not been decl=
ared=20
> W:/Dev-Cpp/include/c++/cstdio:178: error: `__gnu_cxx::vfscanf' has not =
been declared=20
> W:/Dev-Cpp/include/c++/cstdio:179: error: `__gnu_cxx::vscanf' has not b=
een declared=20
> W:/Dev-Cpp/include/c++/cstdio:181: error: `__gnu_cxx::vsscanf' has not =
been declared

I guess you have mixed versions of c++ headers.
Delete everything from W:/Dev-Cpp/include/c++/ then copy all files and=20
dirs from the downloaded gcc-g++-3.4.0-***/include/c++/3.4.0/ to=20
W:/Dev-Cpp/include/c++/

--
Greetings,
   Bal=E1zs

Re: [Dev-C++] Where can I get it?

[<or...@vp...>]

Guillermo Gutierrez wrote:
> is there any thing else that would need to be updated for mingw to work=
?

No.

Here's what you can do, as a last resort:
Completely delete everything from
Dev-Cpp/bin
Dev-Cpp/lib
Dev-Cpp/include

Download the latest installer version of MinGW. Install it.
Add <MinGW installation path>/bin to you PATH environment variable.

Now, unpack the two gcc 3.4 upgrades (gcc-g++-3.4.0-*** and=20
gcc-core-3.4.0-***) into the MinGW install, overwriting everything.
I also recommend to download the latest W32Api (2.5 is the latest, as I=20
remember), and also unpack it (though it is not needed for gcc 3.4 to wor=
k).

That's it. Now you don't even any compilers to be set up in Dev-C++, as=20
it will be automatically found, because <MinGW>/bin is added to the=20
path, and gcc will find it's own includes and libs automatically.

--
Greetings,
   Bal=E1zs

Re: [Dev-C++] Where can I get it?

[<sp...@po...>]

OROSZI Balázs wrote:

> Guillermo Gutierrez wrote:
>
>> is there any thing else that would need to be updated for mingw to work?
>
>
> No.
>
> Here's what you can do, as a last resort:
> Completely delete everything from
> Dev-Cpp/bin
> Dev-Cpp/lib
> Dev-Cpp/include

there's also Dev-Cpp\mingw

>
> Download the latest installer version of MinGW. Install it.
> Add <MinGW installation path>/bin to you PATH environment variable.
>
> Now, unpack the two gcc 3.4 upgrades (gcc-g++-3.4.0-*** and 
> gcc-core-3.4.0-***) into the MinGW install, overwriting everything.
> I also recommend to download the latest W32Api (2.5 is the latest, as 
> I remember), and also unpack it (though it is not needed for gcc 3.4 
> to work).
>
> That's it. Now you don't even any compilers to be set up in Dev-C++, 
> as it will be automatically found, because <MinGW>/bin is added to the 
> path, and gcc will find it's own includes and libs automatically.

AFAIK when you create a c++ project you have to adjust your include 
paths to match mingw version (currently it's 3.2)

According to this page:
http://www.bloodshed.net/dev/devcpp.html
this is the mingw that was used:
ftp://ftp.nanotech.wisc.edu/pub/khan/gnu-win32/mingw32/snapshots/gcc-3.0-1/

AFAIK those components were used in current dev-cpp 5:
gdb-5.1.1-1-mingw.tar.gz
w32api-2.2.tar.gz
mingw-runtime-2.4.tar.gz
make-3.79.1-20010722.tar.gz
one of gcc-3.2 releases (with patches?)
one of binutils-2.13.90 releases (with patches?)

so basicly you would need to update those.

I think it would be good to start testing those and see the what's 
happening. mingw gcc 3.4.0 is still a cadidate.
I think it would be fairly easy to create a packman entries and then 
devpaks for with mingw components and then just upgrade them. This 
wouldn't make
as big of a mess than just unzipping the components.
Maybe I'll spend some thime on that and post the results later here....

--
Marek Januszewski

Re: [Dev-C++] Where can I get it?

[<or...@vp...>]

sp...@po... wrote:
> I think it would be good to start testing those and see the what's=20
> happening. mingw gcc 3.4.0 is still a cadidate.
> I think it would be fairly easy to create a packman entries and then=20
> devpaks for with mingw components and then just upgrade them. This=20
> wouldn't make
> as big of a mess than just unzipping the components.

Due to the stupid layout of Dev-C++'s MinGW "bundle", paths have to be=20
adjusted, otherwise the compiler will not find it's headers and=20
libraries. If you just do as I posted before, everything will work=20
correctly, without adjusting anything. The compiler is packaged to find=20
it's own (standard C and C++) headers and libraries automatically if=20
everything is put in the right place: that is, where the installer puts=20
them.

gcc 3.4 has nothing to do with

gdb
w32api
mingw-runtime
make
binutils

Those are separate packages, not needed to be upgraded to use gcc 3.4
Besides, the right way of upgrading is unzipping. If you ever took a=20
look at the inner layout of the .tar.gz archives of the MinGW packages,=20
you would have noticed, that they all have the same directory layout,=20
which is the same, that is created by the installer, so unzipping will=20
not create any mess anywhere. It will make everything get to the right=20
place.

gcc 3.4 works like a charm for me, and it took less than 20 seconds to=20
upgrade after download.

--
Greetings,
   Bal=E1zs

Re: [Dev-C++] Where can I get it?

[<sp...@po...>]

OROSZI Balázs wrote:

[..]

> Due to the stupid layout of Dev-C++'s MinGW "bundle", paths have to be 
> adjusted, otherwise the compiler will not find it's headers and libraries.

dev-cpp doesn't have a layout any other than standar mingw bins. The 
.tar.gz's provided by them were just untarred to c:\dev-cpp directory. 
No paths were changed.

[..]

> Those are separate packages, not needed to be upgraded to use gcc 3.4
> Besides, the right way of upgrading is unzipping. If you ever took a 
> look at the inner layout of the .tar.gz archives of the MinGW 
> packages, you would have noticed, that they all have the same 
> directory layout, which is the same, that is created by the installer, 
> so unzipping will not create any mess anywhere. It will make 
> everything get to the right place.
>
yes. but some c++ programs will require paths like:
lib\gcc\mingw32\3.4.0\include
(this one is in gcc-core-3.4)
which contains mingw version - currently in dev-cpp it's by default hard 
set to:
lib\gcc-lib\mingw32\3.2\include

For more details look at bug 910098 reported by kidkat and links to 
mingw from there.

--
Marek Januszewski