Turns out that the issue was that libvirt was building with glusterfs
support (detected) and gluster was using flex but it was broken because
of how I compiled it. The solution was to static flex into glusterfs
then rebuild libvirt.
Hopefully that helps someone else....
schu
On 03/01/2016 12:53 PM, Matthew Schumacher wrote:
Hello List,
I'm trying to get libvirt to work on slackware64-current
(slackware64-14.2 beta) and while it compiles just fine, it refuses to
run because of an undefined symbol:
2016-03-01 20:09:26.822+0000: 27849: error : virDriverLoadModule:73 :
failed to load module
/usr/lib64/libvirt/connection-driver/libvirt_driver_storage.so
/usr/lib64/../lib64/libfl.so.2: undefined symbol: yylex
I'm not really doing anything odd, here is my configure options in my
package building script:
./configure \
--prefix=/usr \
--libdir=/usr/lib64 \
--bindir=/usr/sbin \
--sbindir=/usr/sbin \
--sysconfdir=/etc \
--localstatedir=/var \
--mandir=/usr/man \
--docdir=/usr/doc/libvirt-1.3.3 \
--enable-static=no \
--enable-shared=yes \
--with-yajl \
--with-python=/usr \
--with-qemu-group=users \
--with-init-script=none \
--with-storage-iscsi
Looks like the old slackware64-14.1 had flex compiled statically and the
new version is an SO, so I figure that's why this didn't happen on the
older slackware.
Any thoughts on how to fix this?
_______________________________________________
libvirt-users mailing list
libvirt-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users