Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Jun 2020 12:59:22 +0000
From:      bugzilla-noreply@freebsd.org
To:        fortran@FreeBSD.org
Subject:   [Bug 246887] catch Mk/Uses/fortran.mk up to bsd.gcc.mk r301973
Message-ID:  <bug-246887-37611-62nCKqwnWX@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-246887-37611@https.bugs.freebsd.org/bugzilla/>
References:  <bug-246887-37611@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=246887

Tijl Coosemans <tijl@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|ports-bugs@FreeBSD.org      |

--- Comment #5 from Tijl Coosemans <tijl@FreeBSD.org> ---
(In reply to Mark Linimon from comment #3)
> My current view is that the case of USE_GCC=<anything> and USES+=fortran does not even work now.

That is somewhat intentional.  We want all Fortran ports to be compiled with
the same compiler and that implies the same USE_GCC.  Not doing so is asking
for trouble with runtime libraries.  If a port needs a newer version it should
set IGNORE directing the user to modify his DEFAULT_VERSIONS.  If it's stuck on
an older version it should probably set BROKEN with a similar message.

If I were the maintainer of bsd.gcc.mk I would do the same there.  It's simpler
to maintain.  It makes it more likely that users have only one version of gcc
installed and therefore have fewer problems with runtime libraries which means
there are fewer support questions to deal with.  And marking old ports BROKEN
allows us to get rid of them faster, or it might incentivise their maintainers
to fix them with newer gcc faster.

Anyway, what I'm trying to say is, please don't introduce any of the bsd.gcc.mk
"magic" in fortran.mk.  Making it possible to choose "10-devel" as gcc default
would be nice though.

-- 
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-37611-62nCKqwnWX>