| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: make --enable-depend the default |
| Date: | 2013-08-05 21:59:39 |
| Message-ID: | CA+Tgmob2d7G1VozSrzcHmAB-7n_=SKXLbesdHF7RmtFDUhMeaA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 5, 2013 at 4:18 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On Thu, 2013-08-01 at 11:10 +0200, Andres Freund wrote:
>> People, including me, every now and then forget to pass --enable-depend
>> to configure (when not using my own environment). Which then leads to
>> strange errors that cost time to track down...
>
> One argument against that is that we only support dependency tracking
> with GCC, so we would have to either fail configure or use a different
> default depending on the compiler.
>
> It's also unreasonable to assume, I think, that just turning on
> --enable-depend by default will eliminate forgot-a-configure-option
> mistakes. In most cases, you want to turn on most or all --enable-* and
> --with-* options to get good build and test coverage.
Yeah, I have alias dev-configure='./configure
--appropriate-stuff-for-this-machine' on every system where I work on
PG. I imagine others do something similar.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2013-08-05 22:10:24 | Re: don't own lock of type? |
| Previous Message | Robert Haas | 2013-08-05 21:58:13 | Re: don't own lock of type? |