small doubt regarding gcc_select ...
Peter Danecek
Peter.Danecek at bo.ingv.it
Mon May 19 06:38:28 PDT 2014
Well,
given the fact that the select ports influences mainly user's system behaviour, not macports itself, I intentionally posted to the user list, as users might want to express preferences. But of cause we can discuss this elsewhere and I will comment on the ticket that was created.
Here the link:
https://trac.macports.org/ticket/43734
~petr
On 17 May 2014, at 01:55, Mihai Moldovan <ionic at ionic.de> wrote:
> In case not everyone is following -users... and it's more dev-related anyway.
>
> My personal opinion is to also create a symlink for cc.
>
>
> -------- Original Message --------
> Subject: small doubt regarding gcc_select ...
> Date: Mon, 12 May 2014 17:59:01 +0200
> From: Peter Danecek <Peter.Danecek at bo.ingv.it>
> To: MacPorts Users <macports-users at lists.macosforge.org>
>
>
>
> Hi all,
>
> I just realised that `port select gcc` sets /opt/local/bin/c++ -> /opt/local/bin/c++-mp-4.8, while there is no corresponding link for `cc`.
>
> It might be consistent with the fact that there is always a `c++` binary installed by the gcc ports and there is no corresponding `cc` binary. However, I find it a bit confusing (and error prone) that when gcc select is set in some way, a simple `c++` in general would use /opt/local/bin/c++ and point to a Macport gcc version, while `cc` would resolve to `/usr/bin/cc`.
>
> Would it not be cleaner to either
> - point also cc to `/opt/local/bin/gcc`
> or
> - not creating the `/opt/local/bin/c++`
> so that `cc` and `c++` both point to the same compiler suite?
>
> I know that this might be considered a quite minor issue and/or personal taste. On the other hand, `cc` and `c++` are often used as defaults, so it might be relevant to quite some users.
>
> Any considerations?
> ~petr
>
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1762 bytes
Desc: not available
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20140519/cbad4f43/attachment.p7s>
More information about the macports-dev
mailing list