Done.
---
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Perhaps it can be paired down now by someone who understands the perl
> > builds but at this point I just put the configure.in part back, and ran
> >
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Perhaps it can be paired down now by someone who understands the perl
> builds but at this point I just put the configure.in part back, and ran
> autoconf.
I think all that ought to be done is change the description of the
--with-perl option to mention
Bruce Momjian wrote:
> OK, fixed. Marc removed the perl tests because he was removing
> interfaces/perl5, but we still need it for pl/perl and psql's use of
> perl for the help files.
>
> Perhaps it can be paired down now by someone who understands the perl
> builds but at this point I just pu
OK, fixed. Marc removed the perl tests because he was removing
interfaces/perl5, but we still need it for pl/perl and psql's use of
perl for the help files.
Perhaps it can be paired down now by someone who understands the perl
builds but at this point I just put the configure.in part back, an
Joe Conway <[EMAIL PROTECTED]> writes:
> I just sync'd up and am getting:
> make[4]: Leaving directory `/opt/src/pgsql/src/port'
> make[3]: PERL@: Command not found
Marc was overenthusiastic about removing perl support from configure.
I'll put it back.
regards, tom lane
I am seeing the same failure ... looking at it...
---
Joe Conway wrote:
> I just sync'd up and am getting:
>
> make[4]: Leaving directory `/opt/src/pgsql/src/port'
> make[3]: PERL@: Command not found
> make[3]: *** [sql_he
