All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] qemu: fix build when python3 is enabled
Date: Mon, 03 Nov 2014 22:58:55 +0100	[thread overview]
Message-ID: <87bnoo2bfk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <5457F97E.7050509@mind.be> (Arnout Vandecappelle's message of "Mon, 03 Nov 2014 22:54:06 +0100")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 > On 03/11/14 22:37, Peter Korsgaard wrote:
 >> commit: http://git.buildroot.net/buildroot/commit/?id=1d21e4c397cbd92d03d09daf4fadffaa79959f55
 >> branch: http://git.buildroot.net/buildroot/commit/?id=refs/heads/master
 >> 
 >> Fixes:
 >> http://autobuild.buildroot.net/results/04e/04ec455e352319a46dc06def1762c65ad28a12a1/
 >> http://autobuild.buildroot.net/results/f19/f1932657912674af444602ac59211b6caf6841ca/
 >> http://autobuild.buildroot.net/results/18a/18a43df80616280506a44ac3abc327ddf0e7b079/
 >> http://autobuild.buildroot.net/results/44c/44c00b50248018c4e81f4fbb1041d35b78f89640/
 >> 
 >> And many others.
 >> 
 >> When python3 for the target is enabled, $(HOST_DIR)/usr/bin/python points to
 >> host-python3, not host-python - Breaking the build. Ensure host-python is used.

 >  There's another potential issue like this in dbus-python, in python-pypcap and
 > in samba4.

Ahh, ok - Do you know if they all need python2.7 or should we just wait
for the autobuilders to know?

-- 
Bye, Peter Korsgaard 

  reply	other threads:[~2014-11-03 21:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 21:37 [Buildroot] [git commit] qemu: fix build when python3 is enabled Peter Korsgaard
2014-11-03 21:54 ` Arnout Vandecappelle
2014-11-03 21:58   ` Peter Korsgaard [this message]
2014-11-03 22:26     ` Arnout Vandecappelle

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=87bnoo2bfk.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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.