From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: Older versions of Linux as build hosts?
Date: Tue, 22 Mar 2011 16:51:02 +0000 [thread overview]
Message-ID: <1300812662.2793.21.camel@scimitar> (raw)
In-Reply-To: <C9AE1F25.3EB2F%madison@cisco.com>
On Tue, 2011-03-22 at 09:40 -0700, Matt Madison wrote:
> Hi,
>
> I know the documentation mentions that you should be running a
> “reasonably current” Linux as your build host, but in my enterprise
> environment I’m stuck with having to run fairly old versions, based on
> RHEL 4 and 5. I’ve got some patches that I’ve been maintaining so I
> can bootstrap Bernard builds on these systems. Is there any interest
> in supporting older systems as build hosts? Any thoughts on how far
> back “reasonably current” is going to be with each Yocto release? I’m
> trying to work with my IT group to upgrade a bit more frequently, and
> for developer workstations, that might be possible, but I’m not sure
> I’ll be able to convince them to do that for servers in our data
> centers.
>
> Is anyone else having this kind of problem?
We have other users suffering with this sort of problem which is why
Richard worked to enable Poky to build an external Python tarball.
This tarball should include what you need (Python + chrpath) to run Poky
on RHEL: http://autobuilder.yoctoproject.org/downloads/miscsupport/
I documented this for CentOS on the Yocto wiki:
https://wiki.yoctoproject.org/wiki/Poky/GettingStarted/Dependencies
Regards,
Joshua
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Centre
prev parent reply other threads:[~2011-03-22 17:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 16:40 Older versions of Linux as build hosts? Matt Madison
2011-03-22 16:48 ` Mark Hatle
2011-03-22 17:00 ` Rifenbark, Scott M
2011-03-22 17:10 ` Matt Madison
2011-03-23 19:36 ` Matt Madison
2011-03-23 19:39 ` Rifenbark, Scott M
2011-03-22 17:01 ` Jeremy Puhlman
2011-03-22 23:24 ` Mark Hatle
2011-03-23 17:48 ` Richard Purdie
2011-03-22 16:51 ` Joshua Lock [this message]
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=1300812662.2793.21.camel@scimitar \
--to=josh@linux.intel.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.