Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 31 May 2020 21:46:12 +0000
From:      bugzilla-noreply@freebsd.org
To:        fortran@FreeBSD.org
Subject:   [Bug 246888] catch Mk/Uses/fortran.mk up to bsd.gcc.mk r301878
Message-ID:  <bug-246888-37611-IWaOw6XmSg@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-246888-37611@https.bugs.freebsd.org/bugzilla/>
References:  <bug-246888-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=3D246888

--- Comment #2 from Gerald Pfeifer <gerald@FreeBSD.org> ---
(In reply to Mark Linimon from comment #0)
> In order to test 246700, fortran.mk needs to catch up to changes
> long-ago made to bsd.gcc.mk.
>
> The general problem is that bsd.gcc.mk cannot handle the idea of "gccX-de=
vel",
> as bsd.gcc.mk was taught to.

First, thanks for catching this, Mark!

Second, I was going to use this for an -exp run for the update to GCC 10
before GCC 10.1 was released and hence lang/gcc10 created.=20

In the meantime GCC 10.1 is out and I suggest that I focus on getting the
lang/gcc10 port in place quickly (=3D tomorrow) and we can then use that for
the -exp run.  If I am right, this means this present issue goes away and
we can close this report - and save you time and us code duplication in
Uses/fortran.mk?

Makes sense? Agreed?

--=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-246888-37611-IWaOw6XmSg>