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

[Olaf Hering <olaf@aepfle.de>]

On Thu, Jun 21, Ian Campbell wrote:

> On Thu, 2012-06-21 at 09:53 +0100, Olaf Hering wrote:
> > On Thu, Jun 21, Ian Campbell wrote:
> > 
> > > On Wed, 2012-06-20 at 23:51 +0100, Matt Wilson wrote:
> > > > Currently shared libraries are automatically installed into /usr/lib
> > > > or /usr/lib64, depending on the supplied --prefix value and
> > > > $(XEN_TARGET_ARCH). Some systems, like recent Debian and Ubuntu releases,
> > > > do not use /usr/lib64, but instead /usr/lib/x86_64-linux-gnu.
> > > > 
> > > > With this change, packagers can supply the desired location for shared
> > > > libraries on the ./configure command line. Packagers need to note that
> > > > the default behaviour on 64-bit Linux systems will be to install shared
> > > > libraries in /usr/lib, not /usr/lib64, unless a --libdir value is provided
> > > > to ./configure.
> > 
> > Perhaps that should be stated in the README, which states to call just
> > configure without options.
> 
> I'd have assumed that it was well understood what options one
> could/should pass to configure? Anybody who's ever built anything on a
> system which uses lib64 must know it, right?

I think you are right, those who build from source will most likely know
that already. I'm building rpm packages so all this configure stuff is
kind of hidden from me.

Olaf