[MacPorts] #60584: Why haven't gcc10 and clang10 been added as compilers for ports?
MacPorts
noreply at macports.org
Thu Jun 4 20:56:27 UTC 2020
#60584: Why haven't gcc10 and clang10 been added as compilers for ports?
----------------------------+--------------------
Reporter: gaming-hacker | Owner: (none)
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.6.2
Resolution: | Keywords:
Port: clang10 |
----------------------------+--------------------
Comment (by kencu):
In the meantime, if you did want to use one of the newer clang versions to
build something, you can use it manually using {{{sudo port select}}} to
select the version of clang you would like to use. As you probably know,
{{{port select --list clang}}} will give you a list of the available
options.
Then to use that version of clang to build a certain port you would force
it manually on the command line like this:
{{{
sudo port -v install MyFavouritePort configure.compiler=macports-clang
}}}
I am not sure if there's any way that that mechanism can be used with the
openmpi ports, though.
This isn't really an error in the clang port, and there's nothing about
{{{clang-10}}} that needs to be fixed, but I guess we'll leave this ticket
open in case somebody else stumbles across it, pending a new base being
released.
Besides it makes me feel better to see tickets attached to ports that I am
working with when I log into the system. Sense of belonging and all that.
--
Ticket URL: <https://trac.macports.org/ticket/60584#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list