1 |
On 08-08-2016 13:45:07 -0500, R0b0t1 wrote: |
2 |
> On Mon, Aug 8, 2016 at 11:23 AM, Lei Zhang <zhanglei.april@×××××.com> wrote: |
3 |
> > "cc" is the standard C compiler name defined in POSIX, so ideally any |
4 |
> > gcc-agnostic programs should use "cc" instead of "gcc". Practically, |
5 |
> > build tools like GNU Make and CMake would be affected as they use "cc" |
6 |
> > implicitly. |
7 |
> |
8 |
> It is not just programs which rely on GNU extensions, but poorly |
9 |
> created scripts that rely on a compiler directly or otherwise break |
10 |
> portability. |
11 |
|
12 |
I'd agree and say "gcc" is hardcoded in many places, that's why I |
13 |
believe Apple includes a gcc which is clang on their systems, same for |
14 |
cc. |
15 |
|
16 |
As a question to Lei, I'm wondering why you chose eselect compiler, and |
17 |
not gcc-config to manage the links. In a way, gcc-config is tailored |
18 |
towards gcc, but it does a lot of things also for the environment. With |
19 |
clang, from my experience, you just want it as drop-in replacement for |
20 |
gcc as it doesn't give you too much issues (on Darwin at least). |
21 |
|
22 |
Fabian |
23 |
|
24 |
|
25 |
-- |
26 |
Fabian Groffen |
27 |
Gentoo on a different level |