Robert Millan <r...@aybabtu.com> writes: > I'm splitting your bug. In the future, please file separate feature > requests in separate reports.
I knew that I'm touching several different features but I didn't want to open separate bugs for them because I didn't know if they are apropriate for this package. > The mingw32 package is a compiler based on GCC with several > win32-related modifications. > > Initially, there was no win32 support in GCC, and using the mingw32 > compiler was the only option. Now that official versions of GCC > support building for the mingw32 runtime in upstream, there's no > reason most users can't use that directly. AFAIK mingw32 was always based on gcc with some patches to make it work properly. The only change now from let's say three years ago is the number of patches applied to original gcc sources to achieve this goal. > And if for some reason the mingw32 package works better for you, you > have that option too. I feel that what I'm writing can be seen as ranting for lack of package but it is not what I intend. I would like to have a packaged crosscompiler for win32 with best available at the moment features. First gcc 4 version released by mingw.org project was 4.4.0 and it was because they thought that not solved problems in earlier versions were too important. Their 4.4 releases contain some additional patches that were not added at that time to official gcc repository and in their opinion without them this version wouldn't be working properly. That's why mingw32 package (which is at 4.2.something) is not a candidate for a working compiler. With a policy of compiling clean gcc as a win32 crosscompiler gcc-mingw32 package probably will also have some major problems. If I correctly remember the most important issues where throwing c++ exceptions across dll boundaries. If it is important I will find this information. >> Additionally I think users would expect those releases to be >> "compatible" with official releases made by mingw.org people. By >> this I mean build configuration of gcc and patches applied in >> official mingw releases. > > No, that's what the mingw32 package is for. Ok. But IMHO it is not far from clean build from gcc and in near future it will be hard to find the difference between those two packages. Regards. -- Tomasz Gajewski -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
