|
From: <or...@vp...> - 2004-05-12 20:29:56
|
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 |