pcp
[Top] [All Lists]

Re: build issue with AC_PROG_AWK

To: nscott@xxxxxxxxxx
Subject: Re: build issue with AC_PROG_AWK
From: Max Matveev <makc@xxxxxxx>
Date: Tue, 25 Mar 2008 16:53:33 +1100
Cc: James Peach <jamespeach@xxxxxxx>, pcp@xxxxxxxxxxx
In-reply-to: <1206423840.29868.340.camel@edge.scott.net.au>
References: <FC71FBC1-38F6-4CA8-A82C-7FFE102A06BF@mac.com> <1206423840.29868.340.camel@edge.scott.net.au>
Sender: pcp-bounce@xxxxxxxxxxx
On Tue, 25 Mar 2008 16:44:00 +1100, Nathan Scott wrote:

 nscott> One issue with that approach is that it only handles AWK,
 nscott> whereas there are a number of programs configure is trying
 nscott> to find.  It also doesn't use the existing mechanism in
 nscott> PCP for handling this, which is the /etc/pcp.env path list
 nscott> I mentioned earlier.

IIRC the idea was to use configure to populate pcp.conf and with it
pcp.env, we didn't want to use pcp.env during configure runs to avoid
circular dependencies and to deal with possible relocation of "bits"
between releases.

max

<Prev in Thread] Current Thread [Next in Thread>