From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: Yocto Mailer <yocto@yoctoproject.org>
Subject: Re: Older versions of Linux as build hosts?
Date: Wed, 23 Mar 2011 17:48:51 +0000 [thread overview]
Message-ID: <1300902531.3018.41.camel@rex> (raw)
In-Reply-To: <4D892FC3.1010306@windriver.com>
On Tue, 2011-03-22 at 18:24 -0500, Mark Hatle wrote:
> On 3/22/11 12:01 PM, Jeremy Puhlman wrote:
> > On 3/22/2011 9:48 AM, Mark Hatle wrote:
> >> 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 have noticed of late, pseudo's definition of clone conflicts with my
> > RHEL 4's definition of clone. Aside
> > from that I haven't noticed any significant issues.
>
> semantics of clone changed between RHEL 4 and RHEL 5. :(
>
> The newer version of pseudo (upstream, not yet in Poky) fixes this issue.
>
> It's still in development, so I wouldn't consider it stable yet -- but the
> reworking of the utility directories is what was needed to identify the differences.
For what its worth, poky master is now moving ahead with new changes so
if you do have updates for master, the tree is open for them.
Cheers,
Richard
next prev parent reply other threads:[~2011-03-23 17:49 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 [this message]
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=1300902531.3018.41.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=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.