| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: $host_cpu -> $target_cpu in configure? |
| Date: | 2019-06-16 20:36:06 |
| Message-ID: | 25433.1560717366@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Noah Misch <noah(at)leadboat(dot)com> writes:
> https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Specifying-Target-Triplets.html
> describes the intended usage. When cross-compiling, $host_cpu is the machine
> able to run the resulting PostgreSQL installation, and $build_cpu is the
> machine creating that installation. PostgreSQL does not contain a compiler
> that emits code as output to the user, so $target_cpu is meaningless. Every
> use of $host_cpu looks correct.
Hmph ... okay, but that's sure a confusing usage of "host".
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-06-16 20:51:21 | Re: Quitting the thes |
| Previous Message | Noah Misch | 2019-06-16 20:33:54 | Re: $host_cpu -> $target_cpu in configure? |