pcp
[Top] [All Lists]

Re: build issue with AC_PROG_AWK

To: markgw@xxxxxxx
Subject: Re: build issue with AC_PROG_AWK
From: Nathan Scott <nscott@xxxxxxxxxx>
Date: Tue, 25 Mar 2008 17:34:56 +1100
Cc: Max Matveev <makc@xxxxxxx>, James Peach <jamespeach@xxxxxxx>, pcp@xxxxxxxxxxx
In-reply-to: <47E894C7.2000903@sgi.com>
Organization: Aconex
References: <FC71FBC1-38F6-4CA8-A82C-7FFE102A06BF@mac.com> <1206423840.29868.340.camel@edge.scott.net.au> <18408.37725.85447.784561@kuku.melbourne.sgi.com> <47E894C7.2000903@sgi.com>
Reply-to: nscott@xxxxxxxxxx
Sender: pcp-bounce@xxxxxxxxxxx
On Tue, 2008-03-25 at 16:59 +1100, Mark Goodwin wrote:
> 
> 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?

Pretty much.  That would break the ability to set the
location/binary via the AWK environment variable though
(at configure/build time).  It might be better to do it
the same way as sed...

test -z "$SED" && AC_PATH_PROG(SED, sed, /bin/sed)
sed=$SED
AC_SUBST(sed)

cheers.

-- 
Nathan


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