| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Ignoring entries generated by autoconf in code tree |
| Date: | 2015-03-30 20:44:42 |
| Message-ID: | 5519B5BA.3090200@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/25/15 10:34 AM, Tom Lane wrote:
> Michael Paquier <michael(dot)paquier(at)gmail(dot)com> writes:
>> When running autoconf from the root tree, autom4te.cache/ is
>> automatically generated.
>> Wouldn't it make sense to add an entry in .gitignore for that?
>
> Personally, I don't want such a thing, as then I would tend to forget
> to remove that cache file. And you do want to remove it. autoconf
> goes pretty berserk if the cache file hangs around across significant
> changes to configure.in, such as if you were to switch branches.
> (Or at least that used to be true --- last time I got burnt by it
> was quite some time ago, but possibly that's just because I'm careful
> about removing the cache file.)
I think you might be confusing it with config.cache?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-03-30 20:50:14 | Re: Ignoring entries generated by autoconf in code tree |
| Previous Message | Peter Eisentraut | 2015-03-30 20:39:34 | Re: Exposing PG_VERSION_NUM in pg_config |