Opened 2 years ago

Closed 13 months ago

Last modified 6 months ago

#53061 closed enhancement (fixed)

i386-mingw32: remove ports, replaced by i686-w64-mingw32

Reported by: mojca (Mojca Miklavec) Owned by: mojca (Mojca Miklavec)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: landonf@…
Port: i386-mingw32-binutils i386-mingw32-gcc i386-mingw32-libunicows i386-mingw32-runtime i386-mingw32-w32api

Description

I would like to suggest removal of the following ports:

  • i386-mingw32-binutils
  • i386-mingw32-gcc
  • i386-mingw32-libunicows
  • i386-mingw32-runtime
  • i386-mingw32-w32api

since the functionality is now provided by the new MinGW-w64 ports (see #40174):

  • i686-w64-mingw32-binutils
  • i686-w64-mingw32-headers
  • i686-w64-mingw32-crt
  • i686-w64-mingw32-gcc-bootstrap
  • i686-w64-mingw32-gcc
  • x86_64-w64-mingw32-binutils
  • x86_64-w64-mingw32-headers
  • x86_64-w64-mingw32-crt
  • x86_64-w64-mingw32-gcc-bootstrap
  • x86_64-w64-mingw32-gcc

Some build instructions are here:

but note the citation:

As of this writing, the MinGW Project does not support any official build of GCC, more recent than GCC-3.4.5, for use as a cross hosted MinGW development tool, on any platform. This is unlikely to change, until after an officially supported stable GCC-4.x version has been released, for native use on the MS-Windows platform.

If you wish to experiment with more recent versions, then please feel free to do so, /.../ However, please understand that we are currently unable to offer you support for such experimental builds in production use.

While they don't say it's impossible to use a newer compiler, using GCC 3.4.5 is literally useless today, and using a newer compiler is both unsupported and much more tricky to get working that by simply fetching MinGW-w64 that supports using basically any given GCC compiler without any patches/modifications at all.

See also #31578.

We have no dependent ports other than wxmsw that most likely nobody uses.

The most we could hypothetically do is provide symlinks from i386-mingw32-gcc to i686-w64-mingw32-gcc etc. I'm not sure if that is too helpful though.

I'm not sure if the ports should be deleted or replaced_by. Given that the new ports provide different binary names, it might be better to delete them.

If anyone objects, please speak now.

Change History (6)

comment:1 Changed 2 years ago by mojca (Mojca Miklavec)

In ed25e98e/macports-ports:

i386-mingw32-binutils: upgrade to 2.25.1-1

  • Upgrade to version 2.25.1-1
  • Add license GPL-3+
  • Remove $Id$ line

Closes: #38304
See: #51935
See: #53061

comment:2 Changed 2 years ago by mojca (Mojca Miklavec)

In dd6de2b3/macports-ports:

i386-mingw32-binutils: upgrade to 2.25.1-1

  • Upgrade to version 2.25.1-1
  • Add license GPL-3+
  • Remove $Id$ line

Closes: #38304
See: #51935
See: #53061

comment:4 Changed 13 months ago by pmetzger (Perry E. Metzger)

I agree with your reasoning.

comment:5 Changed 13 months ago by mojca (Mojca Miklavec)

Owner: set to mojca
Resolution: fixed
Status: newclosed

In 615abad77912759e02fe42a05207bcbe80ddeaad/macports-ports:

i386-mingw32: replace by i686-mingw32-w64

Closes: #53061

comment:6 Changed 6 months ago by mojca (Mojca Miklavec)

In cd6466f60c9e8f02a7d9267c387ff43cb4f0d5d8/macports-ports (master):

wxmsw: remove a broken outdated port

The port is horribly outdated and no longer builds.
(The old MinGW compiler was obsoleted/removed nearly 8 months ago.)

If someone wants to revive this port,
it should be done from scratch anyway.

See: #41787
See: #53061

Note: See TracTickets for help on using tickets.