Re: Tru64/Alpha problems - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Tru64/Alpha problems
Date
Msg-id 44295BF5.9020703@dunslane.net
Whole thread Raw
In response to Re: Tru64/Alpha problems  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Tru64/Alpha problems
List pgsql-hackers
Tom Lane wrote:

>Andrew Dunstan <andrew@dunslane.net> writes:
>  
>
>>Honda Shigehiro has diagnosed the longstanding problems with his 
>>Tru64/Alpha buildfarm member (bear). See below.
>>    
>>
>
>  
>
>>First, it appears that there is a problem with the system getaddrinfo(), 
>>which configure reports as usable, but turns out not to be. Our current 
>>configure test checks the return value of getaddrinfo("", "", NULL, 
>>NULL) but I am wondering if we should test for "localhost" instead of "" 
>>as the first parameter.
>>    
>>
>
>Huh?  That's just an AC_TRY_LINK test, we don't actually execute it.
>If we did, the test would fail on machines where resolution of "localhost"
>is broken, which we already know is a not-so-rare disease ...
>
>I'm not sure that I believe the "getaddrinfo doesn't work" diagnosis
>anyway, seeing that bear gets through "make check" okay.  Wouldn't that
>fail too if there were a problem there?
>
>  
>

Now that I look further into it, this machine was working just fine 
until we made a change in configure, allegedly to get things right on 
Tru64. The first build that went wrong was the one right after 
configure.in version 1.450. I see a report from Albert Chin that this 
patch worked, but the buildfarm member seems to provide counter-proof.


cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why are default encoding conversions
Next
From: Tom Lane
Date:
Subject: Re: Tru64/Alpha problems