| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Mikael Kjellström <mikael(dot)kjellstrom(at)mksoft(dot)nu> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, mikael(dot)kjellstrom(at)gmail(dot)com |
| Subject: | Re: Mixing CC and a different CLANG seems like a bad idea |
| Date: | 2021-11-18 17:31:28 |
| Message-ID: | 2924101.1637256688@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?UTF-8?Q?Mikael_Kjellstr=c3=b6m?= <mikael(dot)kjellstrom(at)mksoft(dot)nu> writes:
> Hm, actually it's:
> CC => "ccache cc",
> CXX => "ccache c++",
> CLANG => "ccache clang",
Right.
> want me to change it to:
> CC => "ccache clang",
> CXX => "ccache c++",
> CLANG => "ccache clang",
What I actually think is we should get rid of the separate CLANG
variable. But don't do anything to the animal's configuration
till that's settled.
BTW, that would presumably lead to wanting to use CXX = "ccache clang++",
too. I think we don't really want inconsistent CC/CXX either ...
although at least configure knows it needs to probe CXX's flags
separately. I suppose another way to resolve this would be for
configure to make a third set of probes to see what switches CLANG
has --- but ick.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-11-18 17:32:44 | Re: Mixing CC and a different CLANG seems like a bad idea |
| Previous Message | Mikael Kjellström | 2021-11-18 17:24:36 | Re: Mixing CC and a different CLANG seems like a bad idea |