Re: compile errors in new PL/Pler

From: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
To: Larry Rosenman <ler(at)lerctr(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: compile errors in new PL/Pler
Date: 2004-07-02 14:50:22
Message-ID: 20040702114929.C69130@ganymede.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2 Jul 2004, Larry Rosenman wrote:

> On Fri, 2 Jul 2004, Tom Lane wrote:
>
>> Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>>>> I am going to bet dollars to donuts that it is your perl version. Perl
>>>> 5.00503 is ancient. Try upgrading to at least 5.6.
>>
>>> Not much I can do about that - it's builtin as part of FreeBSD 4.x
>>> series.
>>
>> Chris isn't the only one who's going to insist on fixing this ;-)
>>
>> $ perl -v
>> This is perl, version 5.005_03 built for PA-RISC2.0
>
> And on FreeBSD 4.x, you can force use of the perl 5.[68] ports by installing
> one of them, and then issuing:
>
> use.perl port
>
> from a root shell.
>
> (It won't help Tom, but will on FreeBSD. )

On a *reasonably* established FreeBSD box, that makes heavy use of perl
(ie. has *alot* of modules installed), I find that installing the port can
be a bit of a hardship ... on new machines, its something that I do
automatically, but it isn't a solution for older boxes, IMHO ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy(at)hub(dot)org Yahoo!: yscrappy ICQ: 7615664

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeroen T. Vermeulen 2004-07-02 14:51:57 Re: [Re] Re: PREPARE and transactions
Previous Message Christopher Kings-Lynne 2004-07-02 14:38:30 Re: compile errors in new PL/Pler