Re: [HACKERS] Re: setsockopt(SO_REUSEADDR) (Re: Call for porting reports) - Mailing list pgsql-ports

From Tom Lane
Subject Re: [HACKERS] Re: setsockopt(SO_REUSEADDR) (Re: Call for porting reports)
Date
Msg-id 3779.955726246@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Re: setsockopt(SO_REUSEADDR) (Re: Call for porting reports)  (Peter Eisentraut <e99re41@DoCS.UU.SE>)
List pgsql-ports
Peter Eisentraut <e99re41@DoCS.UU.SE> writes:
> On Thu, 13 Apr 2000, Tom Lane wrote:
>> That doesn't strike me as sufficient; it is quite likely that that
>> will find a perl 4.  Does your help-building script run on perl 4?

> No idea. Does anyone have Perl 4 and can try it (and fix it)? Surely Perl
> 4 supports regular expressions and flow control.

perl 4.0.36 generates half a dozen minor-looking syntax errors.  Looks
like perl 5 is more forgiving about where you put parentheses.  Also
perl4 doesn't have "my()", only "local()".  Should be easy to fix;
I'll try this weekend.

Given that, I agree that configure should be fixed to look for a perl,
and then the psql Makefile should enable the build rule only if one
was found.  You want to handle that part?

            regards, tom lane

pgsql-ports by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Re: setsockopt(SO_REUSEADDR) (Re: Call for porting reports)
Next
From: Ryan Kirkpatrick
Date:
Subject: Re: [HACKERS] Linux/Alpha and Postgres 7.0 Beta Status