From: Gary Thomas <gary@mlbassoc.com>
To: Tim Bird <tim.bird@am.sony.com>
Cc: yocto@yoctoproject.org
Subject: Re: Still having build problems - what version of python is required?
Date: Thu, 02 Dec 2010 11:56:56 -0700 [thread overview]
Message-ID: <4CF7EBF8.90609@mlbassoc.com> (raw)
In-Reply-To: <4CF7EB4A.3010109@am.sony.com>
On 12/02/2010 11:54 AM, Tim Bird wrote:
> So I gave up, for the time being, trying to build behind
> my firewall.
>
> I tried to set up a machine outside my firewall to do a build.
> Unfortunately, this machine is a bit dated. It is running
> Fedora 8, with python version 2.5.1.
You need at least 2.6
> Here's what I get when I run bitbake:
>
> [tbird@tree poky-4.0-build]$ bitbake poky-image-minimal
> File "/a/home/tbird/work/yocto/poky-laverne-4.0/scripts/..//bitbake//bin/bitbake", line 207
> except Exception as e:
> ^
> SyntaxError: invalid syntax
> [tbird@tree poky-4.0-build]$ python --version
> Python 2.5.1
> [tbird@tree poky-4.0-build]$ cat /etc/issue
> Fedora release 8 (Werewolf)1
>
> What version of python is required?
>
> Note also that I couldn't find a prce package for this distro, despite
> there being an prce-devel page available. I don't know how important
> that will be for building stuff.
>
> Is it a dead end trying to get a host distro this old to build
> poky?
Probably yes. Can't you upgrade? Fedora 8 is really old now...
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-12-02 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 18:54 Still having build problems - what version of python is required? Tim Bird
2010-12-02 18:56 ` Gary Thomas [this message]
2010-12-02 19:05 ` Joshua Lock
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=4CF7EBF8.90609@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=tim.bird@am.sony.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.