This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Installation question.
- From: Segher Boessenkool <segher at kernel dot crashing dot org>
- To: Iain Sandoe <iain at sandoe dot co dot uk>
- Cc: gcc at gcc dot gnu dot org, law at redhat dot com
- Date: Sun, 12 May 2019 13:01:21 -0500
- Subject: Re: Installation question.
- References: <503172C3-9F80-445C-919A-783D2AC24107@sandoe.co.uk>
On Sun, May 12, 2019 at 03:53:53PM +0100, Iain Sandoe wrote:
> Right now, we don’t install a “cc” [we install gcc] but we do install “c++” [ we also install g++, of course].
>
> Some configure scripts (and one or two places in the testsuite) do try to invoke ‘cc’ which can lead to inconsistent tools being used, if a GCC install is ahead in the PATH of some other install which does provide cc.
>
> Is there a reason for this omission, or is it unintentional?
"cc" isn't POSIX, since over a decade I think. "c99" is POSIX, and it is
a shell script calling whatever "gcc" is first in the PATH, on most distros.
Many scripts that call "cc" expect to find a K&R compiler, historically at
least -- maybe all such scripts went the way of the dodo, that wouldn't be
so bad.
I don't know about "c++", and it is pretty much impossible to search for.
Jeff added it in <https://gcc.gnu.org/r34527>, maybe he can clarify? But
that was quite some time ago ;-)
Segher