Max Matveev wrote:
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.
Yes that's pretty much the explanation, thanks Max. Nowdays I think
we could probably nuke the search for awk in configure and just
statically define it as PCP_AWK_PROG=awk in pcp.conf.in. That assumes
awk will be found in the default path on all required distros .. is
that true?
Cheers
--
Mark Goodwin markgw@xxxxxxx
Engineering Manager for XFS and PCP Phone: +61-3-99631937
SGI Australian Software Group Cell: +61-4-18969583
-------------------------------------------------------------
|