Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)postgresql(dot)org>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Date: 2010-01-05 03:57:33
Message-ID: 20100105035733.GS3778@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Greg Stark escribió:

> I think there's a trick to cover this case but I don't recall what it is.
> 
> Does generating a stamp file help? If you had a rule saying to trigger
> generating the output files because the stamp file is out of date
> which might or might not touch the .h file which would trigger more
> files to be rebuilt then everything should work.... except I fear this
> leads us back to the "make rule which generates two files" problem...

That doesn't work because the files being generated are headers, and
thus they are detected as dependent files automatically by gcc's -MMD
feature (--enable-depend)

Maybe there's a way to make it work but this is not it.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-01-05 04:03:01
Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Previous:From: Robert HaasDate: 2010-01-05 03:55:37
Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting

pgsql-committers by date

Next:From: Tom LaneDate: 2010-01-05 04:03:01
Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Previous:From: Tom LaneDate: 2010-01-05 03:56:53
Subject: pgsql: Fix a few places where we needed -I.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group