Date: Fri, 27 Nov 2020 05:50:29 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 237213] [NEW PORT] devel/mingw-w64 cross compilers Message-ID: <bug-237213-7788-orFM0SkFlD@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 #21 from Damjan Jovanovic <damjan.jov@gmail.com> --- (In reply to Gerald Pfeifer from comment #20) > As a minor detail, new ports don't carry PORTREVISION. Thank you, fixed. > Is there a specific reason you don't autogenerate pkg-plist like the > lang/gcc* ports do? Because I learned from the bad pkg-plist practices in devel/binutils instea= d. > More generally, how hard would it be to use the existing lang/gcc10 > port, like you have been doing with binutils? It looked to me like lang/* are for host-targeting compilers, while devel/*= are for cross-compilers (devel/powerpc64-gcc, devel/gcc-arm-embedded, etc.). If that's not the case, then maybe lang/gcc10 should be used as the GCC for mingw-w64. --=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-orFM0SkFlD>