[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: The mingw* mess in Debian



Hi,

It's even more complex than that, actually:

mingw32 contains gcc 4.2.1 for 32-bit targets

gcc-mingw32 contains gcc 4.4.4 for 32-bit targets. IIRC is not an
official mingw.org release, this may be the reason why there is
mingw32 and gcc-mingw32.

gcc-mingw-w64 contains gcc 4.6 for both 32-bit and 64-bit targets.
IMHO it would be better if it were split in two packages, one for
32-bit targets and the other for 64-bit targets.



On Wed, Nov 9, 2011 at 1:33 PM, Fabian Greffrath <fabian@greffrath.com> wrote:
> Dear -devel,
>
> is there a reason why we have both a mingw32 and a gcc-mingw32 package in
> Debian? Both seem to contain the same, i.e. the GCC from the MinGW project
> (please note they dropped the "32" for a while), but the version in
> gcc-mingw32 is newer than the one in mingw32.
>
> For the 64-bit variant, there is a meta-package called mingw-w64 that pulls
> in gcc-mingw-w64 and mingw-w64-dev. However, for the 32-bit variant, the
> mingw32 package is not a meta-package but (an ancient version) the actual
> compiler, as stated above.
>
> Then, some the package names are also inconsistent, compare mingw32-binutils
> and binutils-mingw-w64.
>
> Is there a principle behind all this or where can I help to clean this up?
> ;)
>
> Cheers,
> Fabian
>
>
> --
> To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> Archive: 4EBA730A.7060707@greffrath.com">http://lists.debian.org/4EBA730A.7060707@greffrath.com
>
>



-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)


Reply to: