On Mon, 2012-07-16 at 18:04 -0400, Frank Ch. Eigler wrote:
> ...
> The intent was to make it possible for a distro package-maker script
> to exactly replicate the status quo ante, with judicious use of the
> old+new configure --FOOdir=/path --with-BARdir=/path options. I
> neglected to demonstrate it for the RPM build, but will do so anon.
Good, that was my expectation.
I've run into a problem (on SuSE, but I suspect it may be more
widespread). 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
+ as_fn_append ac_configure_args0 ' '\''--libexecdir=/usr/share/pcp'\'''
++ ac_configure_args0+=' '\''--libexecdir=/usr/share/pcp'\'''
+ as_fn_append ac_configure_args1 ' '\''--libexecdir=/usr/share/pcp'\'''
++ ac_configure_args1+=' '\''--libexecdir=/usr/share/pcp'\'''
+ as_fn_append ac_configure_args ' '\''--libexecdir=/usr/share/pcp'\'''
++ ac_configure_args+=' '\''--libexecdir=/usr/share/pcp'\'''
++ libexecdir='${exec_prefix}/lib' <===== BAD
++ ac_val=--libexecdir=/usr/share/pcp
++ ac_val=--libexecdir=/usr/share/pcp
++ ac_val=' '\''--libexecdir=/usr/share/pcp'\'''
++ ac_val=--libexecdir=/usr/share/pcp
++ printf '%s\n' ' '\''--libexecdir=/usr/share/pcp'\'''
++ ac_val=--libexecdir=/usr/share/pcp
++ ac_val=' '\''--libexecdir=/usr/share/pcp'\'''
++ printf '%s\n' ' '\''--libexecdir=/usr/share/pcp'\'''
++ ac_val=--libexecdir=/usr/share/pcp
++ ac_val=' '\''--libexecdir=/usr/share/pcp'\'''
+ printf '%s\n' 'libexecdir='\''${exec_prefix}/lib'\'''
This means we can't override PCP_BINADM_DIR because the value for this
one is driven off $libexecdir.
I can't see an alternative in the configure command line options that we
could use, but may be the solution lies somewhere else.
So for the moment, I'm stuck on this one in terms of trying to make the
paths in the packages the same between the old world and the new world.
|