Re: --with-perl=/path/to/prefered/perl? - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: --with-perl=/path/to/prefered/perl?
Date
Msg-id Pine.LNX.4.21.0010252048590.790-100000@peter.localdomain
Whole thread Raw
In response to Re: --with-perl=/path/to/prefered/perl?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: --with-perl=/path/to/prefered/perl?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian writes:

> > Larry Rosenman <ler@lerctr.org> writes:
> > > Would it be possible to add a path spec to the --with-perl configure
> > > option so that if we have 2 or more PERL versions on the system we can
> > > pick which one to use? 
> > 
> > Why do you need that, as opposed to just setting your PATH so that
> > configure finds the right one first?
> 
> On BSD/OS, there is perl (perl4) and perl5 (perl5).  You have to set the
> name of the perl executable.

The standard interface to any Autoconf configure script to override the
name of a program has always been and will always be setting environment
variables like this:

PERL=perl3 CC=cc YACC='bison -y' TCLSH=/usr/local/bin/tclsh AWK=mawk ./configure --options ...

(Okay, I lied, in Autoconf 2.50-to-be you can also put the variable
assignments after the "./configure", but that doesn't change the overall
principle.)

The idea here is that you might set some of these environment variables
permanently on your system and then every configure script you run will
use the same defaults.

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: Larry Rosenman
Date:
Subject: Re: --with-perl=/path/to/prefered/perl?
Next
From: Tom Lane
Date:
Subject: Re: failed runcheck