qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P. Berrange" <berrange@redhat.com>,
	Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] git master build failure in 9pfs
Date: Fri, 3 Mar 2017 16:41:59 +0100	[thread overview]
Message-ID: <20170303164159.5f9a1799@bahia.lan> (raw)
In-Reply-To: <CAFEAcA9WO4f9PuN=f1T61WjTsA8Veq4vERuucQfg-ZRAN0uT8Q@mail.gmail.com>

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

On Thu, 2 Mar 2017 18:10:29 +0000
Peter Maydell <peter.maydell@linaro.org> wrote:

> On 2 March 2017 at 17:40, Daniel P. Berrange <berrange@redhat.com> wrote:
> > On Thu, Mar 02, 2017 at 05:28:24PM +0000, Mark Cave-Ayland wrote:  
> >> Build platform is Debian Wheezy on an x86_64 host.  
> >
> > IIUC, O_PATH was introduced in glibc 2.14 and Wheezy only has 2.13.
> >
> > So unless we want to make this 9pfs code a configurable option, this
> > means Debian Wheezy is no longer a supportable platform for QEMU.  
> 
> I suspect some of our other supported host OSes still have
> glibc 2.13 as well.
> 
> I think we should make this a configure check (assuming O_PATH
> is a hard requirement for 9p now).

No it's not. It can be defined to 0 if doesn't exist.

BTW, I only discover now about this problem... Mark, please Cc me next time
for 9p related problems.

Cheers.

--
Greg

> We already only build 9pfs if
> we're on a Linux host and have the libcap and libattr libraries available.
> 
> thanks
> -- PMM
> 


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

  reply	other threads:[~2017-03-03 15:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 17:28 [Qemu-devel] git master build failure in 9pfs Mark Cave-Ayland
2017-03-02 17:40 ` Daniel P. Berrange
2017-03-02 18:10   ` Peter Maydell
2017-03-03 15:41     ` Greg Kurz [this message]
2017-03-03 14:43   ` Mark Cave-Ayland
     [not found] <mailman.56353.1488479169.22739.qemu-devel@nongnu.org>
2017-03-03  0:30 ` Programmingkid
     [not found] <mailman.56273.1488553194.22740.qemu-devel@nongnu.org>
2017-03-03 15:28 ` G 3
2017-03-03 15:44   ` Greg Kurz
2017-03-03 15:55     ` G 3
2017-03-03 15:58       ` Peter Maydell
2017-03-03 16:02         ` G 3
2017-03-03 16:14         ` Greg Kurz
2017-03-03 16:21       ` Daniel P. Berrange
2017-03-03 16:38         ` G 3
2017-03-03 16:40         ` Eric Blake
2017-03-03 16:42           ` Daniel P. Berrange
2017-03-03 16:45           ` Eric Blake
2017-03-03 16:43         ` Greg Kurz
2017-03-03 18:11           ` Eric Blake
2017-03-03 18:15             ` Greg Kurz
2017-03-03 18:28               ` Eric Blake
2017-03-04 10:57                 ` Greg Kurz

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=20170303164159.5f9a1799@bahia.lan \
    --to=groug@kaod.org \
    --cc=berrange@redhat.com \
    --cc=mark.cave-ayland@ilande.co.uk \
    --cc=peter.maydell@linaro.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).