qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Steve Ellcey <sellcey@imgtec.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Building qemu with old python issue
Date: Wed, 9 Sep 2015 14:17:35 +0100	[thread overview]
Message-ID: <20150909131735.GF22200@redhat.com> (raw)
In-Reply-To: <9795c75a-62c2-4cad-a281-3e45db90439a@BAMAIL02.ba.imgtec.org>

On Tue, Sep 08, 2015 at 12:34:05PM -0700, Steve Ellcey  wrote:
> I am building qemu on an old system with python 2.4.3.  The latest checkin:
> 
>   commit 9d34158a5af734e8de0b42b0a7228200c426a8d0
>   Merge: 8f1ed5f bd80a8a
>   Author: Peter Maydell <peter.maydell@linaro.org>
>   Date:   Mon Sep 7 16:07:47 2015 +0100
> 
>     Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20150907' into staging
> 
> caused my qemu build to fail with:
> 
>   File "/scratch/gcc/nightly/src/qemu/scripts/qapi.py", line 947, in cgen
>     raw = re.subn("^.", indent + r'\g<0>', raw, 0, re.MULTILINE)
>     raw = re.subn("^.", indent + r'\g<0>', raw, 0, re.MULTILINE)
> TypeError: subn() : subn() takes at most 4 arguments (5 given)
> 
> Now the recent patch did not introduce the use of subn, it just seems
> to have changed something so that I call it now whereas before I did not.
> The actual use of subn was introduced with this qemu patch:
> 
>   commit 77e703b861d34bb2879f3e845482d5cf0a3a0ad1
>   Author: Markus Armbruster <armbru@redhat.com>
>   Date:   Wed Jun 24 19:27:32 2015 +0200
> 
>     qapi: Clean up cgen() and mcgen()
> 
> It looks like the 5th (optional) argument to subn in python was added
> with python 2.7 and I am using python 2.4.3.
> 
> Is the use of the 5th argument on subn needed?  And is it intentional
> that qemu cannot be built without a python 2.7 or later?

No, that is a bug. The current intention is for QEMU to be buildable
with Python >= 2.6.0, in order to spport RHEL6 as a min OS version


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 :|

  reply	other threads:[~2015-09-09 13:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-08 19:34 [Qemu-devel] Building qemu with old python issue Steve Ellcey 
2015-09-09 13:17 ` Daniel P. Berrange [this message]
2015-09-09 14:29 ` Eric Blake
  -- strict thread matches above, loose matches on Subject: below --
2015-09-08 16:49 Steve Ellcey 

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=20150909131735.GF22200@redhat.com \
    --to=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sellcey@imgtec.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 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).