Date: Sun, 01 Mar 2020 08:18:34 +0000
From: bugzilla-noreply@freebsd.org
To: ports-bugs@FreeBSD.org
Subject: [Bug 237213] [NEW PORT] devel/mingw-w{32,64} cross compilers
Message-ID: <bug-237213-7788-1JLU3QK25p@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-237213-7788@https.bugs.freebsd.org/bugzilla/>
References: <bug-237213-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237213 --- Comment #8 from Theron Tarigo <theron@freebsd.org> --- Created attachment 212067 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D212067&action= =3Dedit MinGW-w64 for Windows cross-development using LLVM/Clang This ended up being not difficult, albeit using LLVM toolchain, thanks to https://github.com/mstorsjo/llvm-mingw . Of course getting everything done, compiling a working Windows 64bit exe, a= nd seemingly ready to upload the patch only took half the time, other half has been wasted tracking down ridiculous behaviors whereby Clang tries to use GCC-4.x junk instead of its own libraries if the ancient mingw32-* packages= are left installed... At least the fix ended up being simple. When will these developers learn that adding automated workaround disasters= and not documenting them prominently wastes more time than simple errors in the edge-cases they are meant to "fix"? Needs commit or review (I'll put it in the mailing list if no one sees this= ). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-237213-7788-1JLU3QK25p>