From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Bitbake build error on Fedora 12 x86 64-bit
Date: Mon, 25 Jan 2010 06:49:36 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.00.1001250647330.3439@localhost> (raw)
In-Reply-To: <201001250345.51424.holger+oe@freyther.de>
On Mon, 25 Jan 2010, Holger Hans Peter Freyther wrote:
> On Sunday 24 January 2010 16:34:43 Robert P. J. Day wrote:
>
> > > On the other hand I agree totally agree that more testers the
> > > better, but IMO this would also mean that they follow the low
> > > volume bitbake-dev mailinglist, to get information like the
> > > svn->git switch, branches and such?!
> >
> > i'm currently updating the bitbake manual (yes, you should be
> > nervous) and i noticed that there is nothing early on about how to
> > *get* bitbake. so i'm going to add a short section, suggesting
> > first to use the latest official tarball (explaining where to get
> > it), followed by a section for more advanced users on how to check
> > it out, with the appropriate cautions.
>
> Thanks a lot for doing this update.
still working on it, but a question. a while back, i observed that
one of the OE branches (stable/2009?) came with bitbake built in,
while the other i work with (dev) did not. or was it the other way
around? and there was some confusion as to why the situation would be
different between the two branches.
can i document that, no matter what branch one is working with, the
proper approach is to download bitbake separately and make sure that's
the one that's being invoked. (i might add a short side note that
some branches came with bitbake built in, but users should *not* take
advantage of that.)
does that sound reasonable?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
========================================================================
next prev parent reply other threads:[~2010-01-25 11:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 8:01 git pull robin
2010-01-19 8:09 ` robin
2010-01-19 18:37 ` Paul Wilson
2010-01-23 7:22 ` Khem Raj
2010-01-23 11:16 ` Bitbake build error on Fedora 12 x86 64-bit Elvis Dowson
2010-01-23 12:38 ` Elvis Dowson
2010-01-23 12:57 ` Holger Hans Peter Freyther
2010-01-23 13:24 ` Elvis Dowson
2010-01-23 14:51 ` Paul Menzel
2010-01-23 19:40 ` Elvis Dowson
2010-01-23 16:38 ` Holger Hans Peter Freyther
2010-01-24 13:50 ` Robert P. J. Day
2010-01-24 15:10 ` Holger Hans Peter Freyther
2010-01-24 15:34 ` Robert P. J. Day
2010-01-25 2:45 ` Holger Hans Peter Freyther
2010-01-25 11:49 ` Robert P. J. Day [this message]
2010-01-25 12:15 ` Koen Kooi
2010-01-25 12:35 ` Robert P. J. Day
2010-01-23 12:39 ` Graeme Gregory
2010-01-27 16:54 ` Elvis Dowson
2010-01-19 20:13 ` git pull Bjørn Forsman
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=alpine.LFD.2.00.1001250647330.3439@localhost \
--to=rpjday@crashcourse.ca \
--cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox