On Wed, Feb 17, 2021 at 12:11:16AM -0500, George Koehler wrote: > On Wed, 17 Feb 2021 00:23:03 +0100 > Christian Weisgerber <na...@mips.inka.de> wrote: > > Do we want this? Should the port be deleted instead? > > Unless someone updates this, ok gkoehler@ to delete the port. +1
> This port combines gcc 3.4.5 from 2005 with a mingw runtime from 2009 > or 2010 to target Microsoft Windows. I never used this port. I did > use MinGW, with a newer gcc, running on Windows itself, around 2014. > Today, I don't use mingw. > > http://mingw-w64.org/doku.php is a fork of the runtime that targets > both amd64 and i386. (The runtime provides header files and such for > linking to Windows system libraries. You would use the runtime with > the mingw targets of GNU binutils and gcc.) > > https://osdn.net/projects/mingw/ is the original MinGW, has the > runtime for only i386. Years ago, they merged their runtime from > 2 packages (mingwrt, w32api) into 1 (wsl). > > If I would use MinGW today, I would not cross-compile from OpenBSD. > I would first try MSYS2 https://www.msys2.org/ on Windows itself. > MSYS2 uses mingw-w64 and provides bash with gcc (or clang). > > If I would cross-compile from OpenBSD, I would first try to use lld > and clang with the mingw-w64 runtime. If it would work, I would have > skipped compiling gcc and binutils. I would ignore this old port with > its obsolete gcc. --George This reads like a waste of time; for users, porters and package build infrastructure. It is severly outdated and has no amd64 support, I'd rather send it to the attic.
