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

From Alvaro Herrera
Subject Re: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Date
Msg-id 20100105035733.GS3778@alvh.no-ip.org
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting  (Greg Stark <gsstark@mit.edu>)
List pgsql-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


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting