Thanks Eric.
On 01/10/2012 04:01 PM, Eric Blake wrote:
> On 01/10/2012 08:37 AM, Shradha Shah wrote:
>> Hello all,
>>
>> I have been facing an issue when building libvirt using the following steps:
>>
>> 1) ./autogen.sh --prefix=/usr/ --enable-compile-warnings=error
>> 2) make
>> 3) make install
>>
>> The issue is that the above steps puts the binary in /usr/lib instead of /usr/lib64 on a 64 bit OS (RHEL).
>
> That's the correct defaults, according to the GNU Coding Standards which
> autoconf uses in generating the configure script. The fact that
> configure is defaulting --libdir to ${prefix}/lib rather than your
> desired ${prefix}/lib64 means only that RHEL is buggy for not installing
> a config.site override that alters the defaults for it's particular
> choice of preferred libdir; but that's a distro bug [1] that affects
> much more than libvirt, and something that libvirt should not have to
> work around. It does NOT affect rpms built for the the distro, since
> rpms are correctly built with --libdir specified in the right location.
> Meanwhile, the correct way to fix things is by doing:
>
> ./autogen.sh --prefix=/usr --libdir=/usr/lib64
> --enable-compile-warnings=error
>
> In fact, you can even use:
>
> ./autogen.sh --system --enable-compile-warnings=error
>
> as short-hand for setting up _all_ the default paths (including other
> settings, like --sysconfdir=/etc) needed for installing a self-built
> libvirt into the default distro locations on Fedora-based distros,
> including RHEL.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=772997
>
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list