pcp
[Top] [All Lists]

Re: [pcp] fche/prefix branch on pcpfans.git

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] fche/prefix branch on pcpfans.git
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Tue, 17 Jul 2012 20:58:54 -0400
Cc: pcp developers <pcp@xxxxxxxxxxx>
In-reply-to: <1342570967.13871.6.camel@xxxxxxxxxxxxxxxxxxxxxxx>
References: <20120713210843.GC14467@xxxxxxxxxx> <1342476068.9482.46.camel@xxxxxxxxxxxxxxxx> <20120716220400.GG14467@xxxxxxxxxx> <1342570967.13871.6.camel@xxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.4.2.2i
Hi -

On Wed, Jul 18, 2012 at 10:22:47AM +1000, Ken McDonell wrote:
> [...]
> libexecdir seems to be somehow special to the autoconf
> generated part of configure, as in ...
> configure --libexecdir=/path ...
> does not work.  $libexecdir gets set from the command line (good) and
> then gets clobbered unconditionally later (bad) ... here's the trace
> 
> kenj@vm02:~/src/pcpfans$ sh -x ./configure --libexecdir=/usr/share/pcp 2>&1 | 
> grep libexecdir=
> + libexecdir='${exec_prefix}/libexec'
> ++ expr X--libexecdir=/usr/share/pcp : '[^=]*=\(.*\)'
> + libexecdir=/usr/share/pcp                   <===== GOOD
> [...]
> ++ libexecdir='${exec_prefix}/lib'            <===== BAD

That autoconf sure can be a silly git sometimes.

> This means we can't override PCP_BINADM_DIR because the value for this
> one is driven off $libexecdir.

That should be easily worked around: another AC_ARG_WITH for a
pcp_libexecdir in configure.in, and switching derived variables over.


- FChE

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