From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Ångström versions?
Date: Wed, 09 Feb 2011 10:23:51 +0100 [thread overview]
Message-ID: <4D525D27.5030902@dresearch.de> (raw)
In-Reply-To: <4D525A03.2020601@xora.org.uk>
Am 09.02.2011 10:10, schrieb Graeme Gregory:
> On 09/02/2011 07:52, Steffen Sledz wrote:
>> Am 04.02.2011 12:51, schrieb Steffen Sledz:
>>> I'm a bit confused about the Angstrom versions.
>>>
>>> Setting in local.conf is
>>>
>>> DISTRO = "angstrom-2008.1"
>>>
>>> but bitbake reports
>>>
>>> Build Configuration:
>>> BB_VERSION = "1.10.2"
>>> METADATA_BRANCH = "testing-next"
>>> METADATA_REVISION = "3a7b93a"
>>> TARGET_ARCH = "arm"
>>> TARGET_OS = "linux-gnueabi"
>>> MACHINE = "hipox"
>>> DISTRO = "angstrom"
>>> DISTRO_VERSION = "2010.7-test-20110204"
>>> TARGET_FPU = "soft"
>>>
>>> Is this intented?
>>>
>>> BTW: Which is the suggested/released Ångström version? http://www.angstrom-distribution.org/ seems to be not very helpful here. e.g. the FAQ link results in an PAGE NOT FOUND. :(
> 2008.1 is the "stable" version of Angstrom which has all the benefit of
> our extensive toolchain testing.
>
> 2010.x is angstrom-next and is the in progress version moving to gcc 4.5
> blah blah blah.
OK, but why bitbake reports DISTRO_VERSION = "2010.7-test-20110204" if it is set to DISTRO = "angstrom-2008.1" ???
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@DResearch.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2011-02-09 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 11:51 Ångström versions? Steffen Sledz
2011-02-09 7:52 ` Steffen Sledz
2011-02-09 9:06 ` Henning Heinold
2011-02-09 9:10 ` Graeme Gregory
2011-02-09 9:23 ` Steffen Sledz [this message]
2011-02-09 9:30 ` Graeme Gregory
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=4D525D27.5030902@dresearch.de \
--to=sledz@dresearch.de \
--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