|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru>|
|Cc:||James Hilliard <james(dot)hilliard1(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>|
|Subject:||Re: [PATCH 1/1] Fix detection of pwritev support for OSX.|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru> writes:
> I rejected to install CLT and abandoned Homebrew. Then I just cloned and
> built Postgres successfully. So it looks like Xcode is really enough, at
> least on a recent macOS version.
Hm. I seem to recall having had to install CLT as well as Xcode back
in the day, but maybe Apple improved that. On the other side of the
coin, it also seems to be possible to build PG with only CLT and not
Xcode. I didn't try to verify that with a scorched-earth test, but
I did trash Xcode (and empty trash) on my wife's Mac, and I could
still build and "make check" with only the CLT in place.
[ pokes more carefully... ] Ah-hah, I see why I needed the CLT.
I bet you'll find that you can't build from "git clean -dfx" state
with only Xcode, because comparing the contents of
/Library/Developer/CommandLineTools/usr/bin on my own Mac,
I observe that only the CLT provides bison and flex. I also see
install_name_tool only in the CLT; we don't depend on that today,
but may soon (see the latest thread about coping with SIP).
On the whole it looks like we should recommend installing the CLT
and not bothering with Xcode, which is about 10X the size:
$ du -hs /Library/Developer/CommandLineTools
$ du -hs /Applications/Xcode.app
regards, tom lane
|Next Message||Tom Lane||2021-01-22 17:32:16||Re: macOS SIP, next try|
|Previous Message||japin||2021-01-22 16:46:47||Re: About to add WAL write/fsync statistics to pg_stat_wal view|