On 03.03.2012 15:15, Andreas Färber wrote: > Am 03.03.2012 07:43, schrieb ronnie sahlberg: >> Yes, >> >> Very unfortuante since libiscsi is such a nice name for a >> multiplatform library what even works on win32 :-( >> >> I have so renamed it to libiscsiclient and sent a patch to qemu to >> this list to use -liscsiclient instead of -liscsi > > Mind letting us know which library exactly this clashes with (URL)? > According to Hannes there was no clash on openSUSE (which I would call a > standard Linux distro as well), so it sounded like a Fedora-specific > packaging problem to him.
It looks like iscsi-initiator-utils package in fedora is built using shared libiscsi which appears to be package-specific, e.g. http://www.rpmseek.com/rpm/iscsi-initiator-utils-6.2.0.870-13.fc13.x86_64.html?hl=com&cx=0:-:0:8107228:0:0:0: Files: /sbin/iscsi-iname /sbin/iscsiadm /sbin/iscsid /sbin/iscsistart /usr/lib64/libiscsi.so.0 ... I'd rename _that_ library to be libiscsi-initiator-utils.so, to reflect the name of the package in question, since it - again - _appears_ to be package-specific. Thanks, /mjt >> tarballs can be found at >> https://github.com/sahlberg/libiscsi/downloads >> >> >> That resolves all issues you are concerned about ? >> >> >> regards >> ronnie sahlberg >> >> On Tue, Feb 14, 2012 at 12:24 AM, Daniel P. Berrange >> <berra...@redhat.com> wrote: >>> I was investigating how to build latest QEMU with the iSCSI block driver >>> enabled. I saw that configure wanted a libiscsi.so, so I installed that >>> library from Fedora RPMs via the iscsi-initiator-utils package, but it >>> still wouldn't build. >>> >>> After further investigation, I find that QEMU in fact wants a completely >>> different, unlreated libiscsi.so library: >>> >>> https://github.com/sahlberg/libiscsi >>> >>> Obviously we have a problem here because we can't have two different >>> libraries called libiscsi.so installed at the same time. >>> >>> Since iscsi-initiator-utils is a standard Linux distro package whose usage >>> of libiscsi.so predates this github project, it seems that to resolve this >>> it will be neccessary to rename the latter. eg perhaps libiscsi-client.so ? >>> >>> The followup question is where to find actual libiscsi releases to package >>> up for OS distros ? It is not very desirable to just package GIT snapshots. >>> >>> Regards, >>> Daniel >>> -- >>> |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ >>> :| >>> |: http://libvirt.org -o- http://virt-manager.org >>> :| >>> |: http://autobuild.org -o- http://search.cpan.org/~danberr/ >>> :| >>> |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc >>> :| >
