Re: [PATCH 1 of 1 v2] tools: honour --libdir when it is passed to ./configure

[Matt Wilson <msw@amazon.com>]

On Fri, Jun 22, 2012 at 01:26:49AM -0700, Ian Campbell wrote:
> On Thu, 2012-06-21 at 19:43 +0100, Matt Wilson wrote:
> > Confusingly, we also install "private" binaries to $(PRIVATE_BINDIR),
> > which expands to $(PRIVATE_PREFIX)/bin which expands to $(LIBDIR)/xen/bin,
> > which expands to /usr/lib64/xen/bin. This results in paths like:
> > 
> > /usr/lib64/xen/bin/lsevtchn
> 
> ... weird!
> 
> [...]
> 
> > > I suppose configure defines a libexec but it isn't the one we want?
> > 
> > By default, configure will define libexec to be /usr/libexec, which I
> > like. If we switched to using the value provided from configure, we
> > people who don't like /usr/libexec could just provide a different
> > value at ./configure time.
> 
> Lets leave that until 4.3, I'm already a little uncomfortable messing
> with the build system at this stage in 4.2 (there's always unforeseen
> consequences to these sorts of changes, no matter how diligent we all
> are :-/). For the lib vs. lib64 breakage on multiarch I think the risk
> is worth it, but for more "cosmetic" issues like libexec I'd rather pass
> for now.

Agreed. It deserves a little extra attention, since some of the
binaries that might should move to /usr/libexec live outside the
tools/ tree.

Matt