qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: chris@include.gr, jcody@redhat.com, qemu-block@nongnu.org,
	kwolf@redhat.com, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.9] block: Drop unmaintained 'archipelago' driver
Date: Wed, 8 Mar 2017 21:18:37 +0100	[thread overview]
Message-ID: <995ef14c-4a0d-0b9b-db21-743c4cc3d584@redhat.com> (raw)
In-Reply-To: <0eac6b1c-2dc0-b0aa-7392-3b7f344cae48@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]

On 08.03.2017 21:09, Eric Blake wrote:
> On 03/08/2017 02:05 PM, Max Reitz wrote:
>> On 08.03.2017 21:02, Eric Blake wrote:
>>> The driver has failed to build since commit da34e65, in qemu 2.6,
>>> due to a missing include of qapi/error.h for error_setg().
>>> Since no one has complained in three releases, it is easier to
>>> remove the dead code than to keep it around, especially since it
>>> is not being built by default and therefore prone to bitrot.
>>>
>>> Signed-off-by: Eric Blake <eblake@redhat.com>
>>> ---
>>>
>>> My proposed alternative for Max's "block/archipelago: Make it compile"
>>>
>>>  qapi/block-core.json             |   33 +-
>>>  block/archipelago.c              | 1079 --------------------------------------
>>>  MAINTAINERS                      |    8 -
>>>  block/Makefile.objs              |    2 -
>>>  configure                        |   43 --
>>>  tests/qemu-iotests/025           |    2 +-
>>>  tests/qemu-iotests/common        |    6 -
>>>  tests/qemu-iotests/common.filter |    4 +-
>>>  tests/qemu-iotests/common.rc     |    8 -
>>>  9 files changed, 4 insertions(+), 1181 deletions(-)
>>>  delete mode 100644 block/archipelago.c
>>
>> Reviewed-by: Max Reitz <mreitz@redhat.com>
>>
>> But I'd like someone to confirm that I'm not the only one who can't
>> compile archipelago. ;-)
> 
> With my proposed patch not installed, I tried:
> 
> ./config.status --enable-archipelago
> 
> but got the error:
> 
> ERROR: User requested feature Archipelago backend support
>        configure was not able to find it.
>        Install libxseg devel
> 
> 
> I don't see libxseg-devel available for Fedora; where does one get it to
> even attempt compilation?

I got it from https://github.com/grnet/libxseg, and got it to compile by
removing all "python" instances from CMakeLists.txt (including the
find_program() blocks).

Max


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

  reply	other threads:[~2017-03-08 20:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 20:02 [Qemu-devel] [PATCH for-2.9] block: Drop unmaintained 'archipelago' driver Eric Blake
2017-03-08 20:05 ` Max Reitz
2017-03-08 20:09   ` Eric Blake
2017-03-08 20:18     ` Max Reitz [this message]
2017-03-09  3:18       ` Fam Zheng
2017-03-09 13:47 ` Kevin Wolf

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=995ef14c-4a0d-0b9b-db21-743c4cc3d584@redhat.com \
    --to=mreitz@redhat.com \
    --cc=armbru@redhat.com \
    --cc=chris@include.gr \
    --cc=eblake@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).