Re: Ignoring entries generated by autoconf in code tree - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Ignoring entries generated by autoconf in code tree
Date
Msg-id 5519B5BA.3090200@gmx.net
Whole thread Raw
In response to Re: Ignoring entries generated by autoconf in code tree  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Ignoring entries generated by autoconf in code tree  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 3/25/15 10:34 AM, Tom Lane wrote:
> Michael Paquier <michael.paquier@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?




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Exposing PG_VERSION_NUM in pg_config
Next
From: Tom Lane
Date:
Subject: Re: Ignoring entries generated by autoconf in code tree