From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | David Wheeler <david(at)kineticode(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Suggestion: Which Binary? |
Date: | 2006-04-01 01:31:10 |
Message-ID: | 20060401013109.GA18277@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Fri, Mar 31, 2006 at 06:52:51PM -0500, Tom Lane wrote:
> David Wheeler <david(at)kineticode(dot)com> writes:
> > But that's a PITA. I'd much rather have been able to tell configure
> > *which* perl to use:
>
> > ./configure --with-perl=/usr/bin/perl5.8.6
>
> The more usual way to handle this sort of thing is to put each
> version of perl in a different directory, and then you can alter
> PATH while running configure to pick which one you want. I've got
> several versions of perl on this machine that I select that way ...
> it doesn't require any special smarts on the part of the perl-using
> program, and it scales to handle multiple versions of other things
> like Tcl, too.
You mean something more like this?
PATH=/path/to/perl:/usr/bin:/bin ./configure ...
Sounds good, except when the perl people have in mind is on the same
path as other perls. How would changing $PATH help with a situation
like that?
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Rylander | 2006-04-01 01:35:35 | Re: First Aggregate Funtion? |
Previous Message | Agent M | 2006-04-01 01:27:10 | listen not schema-aware |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-04-01 04:02:28 | Re: Suggestion: Which Binary? |
Previous Message | David Wheeler | 2006-04-01 01:11:04 | Re: Suggestion: Which Binary? |