From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Generating configure from configure.ac |
Date: | 2024-11-26 02:16:46 |
Message-ID: | 20241126.111646.1676492470795718645.ishii@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
>> I ran autoconf 2.69 on my Ubuntu 20.04 laptop and got the same diffs
>> plus diffs related runstatedir:
>
>> + --runstatedir=DIR modifiable per-process data [LOCALSTATEDIR/run]
>
>> If my understanding is correct, configure in the git repository has
>> been generated by autoconf 2.69 too. Maybe autoconf 2.69 generates
>> slightly different results depending on platform?
>
> If you use a vendor-supplied package of autoconf, you are likely
> to get such diffs because of vendor patches. The expectation in
> our usage is that committers will use exactly the GNU release
> of autoconf, which is available from
>
> https://ftp.gnu.org/gnu/autoconf/autoconf-2.69.tar.gz
Thanks for the quick response. Ok, the point is always use autoconf
from the original source code, not use the autoconf coming with the
platform.
BTW, in my understanding, patch posters do not need to submit a patch
for configure, a patch for configure.ac is enough since configure will
be generated by committers anyway (if the patch gets committed).
Best reagards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-11-26 02:19:00 | Re: Generating configure from configure.ac |
Previous Message | Tom Lane | 2024-11-26 02:03:05 | Re: Generating configure from configure.ac |