Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154])
	by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0BKe2p42371
	for <pgsql-docs@postgresql.org>; Thu, 11 Jan 2001 15:40:02 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f0BKdiJ12616;
	Thu, 11 Jan 2001 15:39:44 -0500 (EST)
To: "Shane D." <sdawalt@millennium.wright.edu>
cc: pgsql-docs@postgresql.org
Subject: Re: FAQ Update Info 
In-reply-to: <3A5CBBE7.B43C1D12@millennium.wright.edu> 
References: <3A5CBBE7.B43C1D12@millennium.wright.edu>
Comments: In-reply-to "Shane D." <sdawalt@millennium.wright.edu>
	message dated "Wed, 10 Jan 2001 14:45:43 -0500"
Date: Thu, 11 Jan 2001 15:39:44 -0500
Message-ID: <12613.979245584@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200101/36
X-Sequence-Number: 170

"Shane D." <sdawalt@millennium.wright.edu> writes:
>   I have found after some trial and error that the actual problem is in
> the configure script.  It assumes cc will be used prior to detecting (or
> processing) the gcc setting.  As a result, it loads the alpha_cc
> template but never loads the alpha_gcc template when gcc is selected. 

I think this should be cleaned up in current sources (7.1beta3).  We've
restructured the template files.  Would you care to give beta3 a try
and see if the behavior is OK now?

			regards, tom lane