Date: Wed, 03 Jun 2020 10:22:22 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 246887] catch Mk/Uses/fortran.mk up to bsd.gcc.mk r301973 Message-ID: <bug-246887-7788-lni55r5mct@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-246887-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-246887-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=3D246887 Mark Linimon <linimon@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|portmgr@FreeBSD.org |linimon@FreeBSD.org --- Comment #3 from Mark Linimon <linimon@FreeBSD.org> --- (In reply to Tijl Coosemans from comment #2) > _GCC_RUNTIME is missing "gcc", it should be "${LOCALBASE}/lib/gcc${_GCC_V= ER}". Then you get the string "gccgcc". That's why I changed it from the first w= ay I had it. > I'm also thinking we should prefix private variables with _FORTRAN or som= ething so they are less likely to interfere with bsd.gcc.mk. My current view is that the case of USE_GCC=3D<anything> and USES+=3Dfortra= n does not even work now. Both of my patches need more work. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246887-7788-lni55r5mct>