small doubt regarding gcc_select ...

[Ryan Schmidt]

Yes, we should. Is there a ticket filed about this bug already? If not, please file one.

On May 16, 2014, at 18: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