Peter Eisentraut <pete...@gmx.net> writes:
> On 3/25/15 10:34 AM, Tom Lane wrote:
>> Michael Paquier <michael.paqu...@gmail.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?
No, I've never used config.cache. I'm not actually sure what autoconf
keeps in autom4te.cache/, but I've definitely seen it generate wacko
output files when that directory still has contents from a previous
run with some other version of the input files.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
