From: "Andreas Färber" <afaerber@suse.de>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: qemu-devel@nongnu.org, Hannes Reinecke <hare@suse.de>
Subject: Re: [Qemu-devel] QEMU desired libiscsi.so clashes with libiscsi.so from iscsi-initiator-utils
Date: Sat, 03 Mar 2012 12:15:30 +0100 [thread overview]
Message-ID: <4F51FD52.6080407@suse.de> (raw)
In-Reply-To: <CAN05THScMrN0TXLWqKGrF=Zhp1tid1qYcrhfzHZTOnpZemGvRw@mail.gmail.com>
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.
Andreas
> 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
> <berrange@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 :|
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-03-03 11:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 13:24 [Qemu-devel] QEMU desired libiscsi.so clashes with libiscsi.so from iscsi-initiator-utils Daniel P. Berrange
2012-03-03 6:43 ` ronnie sahlberg
2012-03-03 11:15 ` Andreas Färber [this message]
2012-03-03 11:54 ` Michael Tokarev
2012-03-06 10:07 ` Daniel P. Berrange
2012-03-06 10:38 ` Michael Tokarev
2012-03-06 11:06 ` ronnie sahlberg
2012-03-06 11:15 ` Daniel P. Berrange
2012-03-06 14:10 ` Michael Tokarev
2012-03-06 12:19 ` Hannes Reinecke
2012-03-06 19:58 ` Mike Christie
2012-03-06 20:13 ` Mike Christie
2012-03-07 1:51 ` ronnie sahlberg
2012-03-07 2:30 ` Mike Christie
2012-03-06 10:02 ` Daniel P. Berrange
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F51FD52.6080407@suse.de \
--to=afaerber@suse.de \
--cc=hare@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.