I did, the ./configure part looks like this:
./configure \
--prefix=%{_prefix} \
--libdir=%{_libdir} \
--sysconfdir=%{_sysconfdir} \
--interp-prefix=%{_prefix}/qemu-%%M \
--audio-drv-list=pa,sdl,alsa,oss \
--localstatedir=%{_localstatedir} \
--libexecdir=%{_libexecdir} \
--disable-strip \
--extra-ldflags="$extraldflags -pie -Wl,-z,relro -Wl,-z,now" \
--extra-cflags="%{optflags} -fPIE -DPIE" \
--enable-mixemu \
--enable-trace-backend=dtrace \
--disable-werror \
--disable-xen \
--enable-kvm \
--enable-migration-from-qemu-kvm \
--enable-glusterfs \
I too had assumed it would just work.
Thanks,
_
/-\ ndrew
On Tue, May 14, 2013 at 8:39 AM, John Mark Walker <johnmark(a)gluster.org> wrote:
----- Original Message -----
> It looks as though the qemu package is built without Gluster support.
> So I added the --with-glusterfs flag and tried to rebuilt the RPM. I
Did you do ./configure --enable-glusterfs ?
> am now getting this error:
>
> ERROR
> ERROR: User requested feature GlusterFS backend support
> ERROR: configure was not able to find it
> ERROR
>
> What is configure looking for that it can't find? Again
> glusterfs-server and glusterfs-devel packages are installed.
>
Adding devel@fedora and moving to gluster-devel.
Is there a way to change default flags for qemu compilation? Who's the maintainer? I
had assumed that manually changing the flags to include --enable-glusterfs would do the
trick.
After doing a little digging, I see QEMU is owned by "virtmaint" which I assume
is an alias for several people.
Can anyone confirm the ability or inability to build QEMU with GlusterFS support on F19?
I'm running F18 and can download 1.4 from
qemu.org, which builds (and runs) just
fine.
-JM
--
_
/-\ ndrew Niemantsverdriet
Linux System Administrator
Academic Computing
(406) 238-7360
Rocky Mountain College
1511 Poly Dr.
Billings MT, 59102