From: Mark Hatle <mark.hatle@windriver.com>
To: <yocto@yoctoproject.org>
Subject: Re: Bitbake requires Python 2.7.3
Date: Fri, 28 Jun 2013 12:03:43 -0500 [thread overview]
Message-ID: <51CDC1EF.5020803@windriver.com> (raw)
In-Reply-To: <CAJTo0LZV0dUDb9XqyTuiwCGMUEyVFX1qX5=ngUp+zbxVYFV-hQ@mail.gmail.com>
On 6/28/13 5:53 AM, Burton, Ross wrote:
> On 28 June 2013 11:16, Paul Barker <paul@paulbarker.me.uk> wrote:
>> Just chiming in to say that sounds excellent. Will this contain a
>> known-working make as well for those with a broken make 3.82?
>
> What systems have a broken 3.82? I'm aware that Debian Experimental
> has it, but stable/testing/unstable have a working 3.81. Certain
> older versions of Suse also had a broken 3.82, but they've been fixed
> recently after I filed some bugs. Is it just Fedora 16?
Fedora 16 and newer
Arch Linux
Debian Experimental
I wouldn't be surprised if there are others.
(I filed a bug for Fedora, so FC 18 and FC 19 will be fixed if they're not already.)
Someone on the OE-Core list said they would file a bug on Arch Linux.
--Mark
> Ross
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
next prev parent reply other threads:[~2013-06-28 17:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 8:55 Bitbake requires Python 2.7.3 Chris Tapp
2013-06-28 9:06 ` ChenQi
2013-06-28 16:35 ` Chris Tapp
2013-06-28 9:40 ` Paul Eggleton
2013-06-28 10:16 ` Paul Barker
2013-06-28 10:29 ` Paul Eggleton
2013-06-28 10:53 ` Burton, Ross
2013-06-28 17:03 ` Mark Hatle [this message]
2013-06-28 17:07 ` Burton, Ross
2013-07-04 2:48 ` Trevor Woerner
2013-07-04 8:18 ` Burton, Ross
2013-06-28 10:25 ` Rifenbark, Scott M
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=51CDC1EF.5020803@windriver.com \
--to=mark.hatle@windriver.com \
--cc=yocto@yoctoproject.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 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.