| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Karl Denninger <karl(at)denninger(dot)net>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: FreeBSD 12 and Postgres build failures |
| Date: | 2019-03-20 06:31:58 |
| Message-ID: | CA+hUKGJz2YNyXcZpabUpW06o2-4SuuT_r3gyVdLf1YCiPL_PaQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Mar 20, 2019 at 6:41 PM Andrew Gierth
<andrew(at)tao11(dot)riddles(dot)org(dot)uk> wrote:
> ... (Though the fact that we prefer gcc to cc in
> configure if both are found is a decision that should probably be
> revisited, given that the reasons for that preference are mostly
> consigned to the graveyard of commercial Unix variants.)
+1
I'm not against looking for gcc and g++ if cc and c++ can't be found,
but preferring them (ie implying that some random GCC found on the
path that you didn't explicitly ask for must surely be better than
whatever crap the vendor ships) makes no sense in this day and age.
The silliest case is macOS, where gcc and g++ are found and used but
are in fact... wrappers for clang, for maximum confusion.
--
Thomas Munro
https://enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zwettler Markus (OIZ) | 2019-03-20 10:10:04 | Postgres Enhancement Request |
| Previous Message | Andrew Gierth | 2019-03-20 05:40:46 | Re: FreeBSD 12 and Postgres build failures |