Re: Compile fail, alpha5 & gcc 4.3.3 in elog.c - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Compile fail, alpha5 & gcc 4.3.3 in elog.c
Date
Msg-id 1270205574.5813.3.camel@vanquo.pezone.net
Whole thread Raw
In response to Re: Compile fail, alpha5 & gcc 4.3.3 in elog.c  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On fre, 2010-04-02 at 06:42 -0400, Robert Haas wrote:
> Forgive me for being a little annoyed here, but I actually did follow
> that document quite closely. Unfortunately it omits to mention a few
> key points.

Sorry, I had suspected that you didn't do a clean cvs export.  It was a
frequent problem in the old days.

> What actually happened here is that I discovered that I couldn't run
> "make distcheck" on a clean source tree.  configure needs to be run
> first, and the fine documentation makes no mention of what options
> should be used.

Doesn't matter.  Just ./configure is enough.

> So naturally I just ran my dev-configure alias, which
> also creates a one-line Makefile.custom.  Now maybe I should have
> realized that this was going to lead to bad things happening, but I
> didn't.

Ah, well, nothing can guard against that. ;-)

> The wiki page in fact makes no reference at all to the state
> that one's source tree should be in when doing all of this; it just
> didn't occur to me that any random crap I happened to have lying
> around there was going to get shipped.

The state is that after a cvs export.

> I'm obviously very sorry for the hassle and frustration caused by this
> mistake, especially to Dave Page, but hopefully you understand that I
> was trying rather hard to get this right; and perhaps the Wiki page
> can also be improved to mention some of these details.

Please add your findings.




pgsql-hackers by date:

Previous
From: Tatsuhito Kasahara
Date:
Subject: pgstattuple does not contain CHECK_FOR_INTERRUPTS()
Next
From: GenieJapo
Date:
Subject: Re: Compile fail, alpha5 & gcc 4.3.3 in elog.c