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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-01-05 04:03:01 | Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting |
Previous Message | Tom Lane | 2010-01-05 03:56:53 | pgsql: Fix a few places where we needed -I. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-01-05 04:03:01 | Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting |
Previous Message | Robert Haas | 2010-01-05 03:55:37 | Re: [COMMITTERS] pgsql: Remove too-smart-for-its-own-good optimization of not overwriting |