All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Bitbake build error on Fedora 12 x86 64-bit
Date: Mon, 25 Jan 2010 13:15:54 +0100	[thread overview]
Message-ID: <hjk21o$8m0$1@ger.gmane.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1001250647330.3439@localhost>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 25-01-10 12:49, Robert P. J. Day wrote:
> 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?

*If* is has bitbake builtin, users should use that one, as it is certain
that bitbake will match the metadata. You can opt to choose to install a
bitbake yourself, but then it's up to you to make sure bitbake and OE match.
Since stable/2009 is a long term branch we decided to put bitbake in
there to remove at least on point of failure.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLXYt5MkyGM64RGpERAjcZAJ9/EskJ5wwW6yvdkzOXlRBCerbYyACfdOM4
HmGTgPTWrbAexAZv9zpXhqI=
=Tz1I
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-01-25 12:18 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
2010-01-25 12:15                     ` Koen Kooi [this message]
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='hjk21o$8m0$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 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.