All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: Matt Madison <madison@cisco.com>
Cc: Yocto Mailer <yocto@yoctoproject.org>
Subject: Re: Older versions of Linux as build hosts?
Date: Tue, 22 Mar 2011 11:48:16 -0500	[thread overview]
Message-ID: <4D88D2D0.7050202@windriver.com> (raw)
In-Reply-To: <C9AE1F25.3EB2F%madison@cisco.com>

On 3/22/11 11:40 AM, Matt Madison wrote:
> Hi,
> 

I have done builds with both RHEL 4 and RHEL 5.  Both on machines in which I do
not have root access.

For me I was able to simply provide an update python, some additional tools and
it worked.  (Note, I haven't tried it in the last 2 months though, so something
may have broken since then.)

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

I think this is a fairly typical problem.  In my experience it's usually easier
to solve in a commercial space then pure open source.

As for the question about interest, we're always interested in patches.  At a
minimum, it would be nice to document what steps you had to do and what patches
you may have had to apply in order to get "unsupported" functionality out of the
build environment.  The yocto wiki seems a fairly natural place for this.

So please send what you have, or start an account on the Yocto Wiki and post it
there.

--Mark

> Thanks,
> -Matt
> 
> 
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



  reply	other threads:[~2011-03-22 16:48 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 [this message]
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

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=4D88D2D0.7050202@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=madison@cisco.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.