Re: $host_cpu -> $target_cpu in configure?
От | Noah Misch |
---|---|
Тема | Re: $host_cpu -> $target_cpu in configure? |
Дата | |
Msg-id | 20190616203354.GA420587@rfd.leadboat.com обсуждение исходный текст |
Ответ на | $host_cpu -> $target_cpu in configure? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: $host_cpu -> $target_cpu in configure?
|
Список | pgsql-hackers |
On Sun, Jun 16, 2019 at 12:56:52PM -0400, Tom Lane wrote: > There are a few places in configure and the makefiles that are looking > at $host_cpu to decide what to do. As far as I can tell, almost all of > them are wrong and should be looking at $target_cpu instead. (The > lack of complaints indicates that nobody is trying very hard to test > cross-compilation.) 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.
В списке pgsql-hackers по дате отправления: