From: Saul Wold <sgw@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: binutils 2.23 call for testing the recipes
Date: Fri, 16 Nov 2012 11:16:54 -0800 [thread overview]
Message-ID: <50A69126.2070506@linux.intel.com> (raw)
In-Reply-To: <20121116080712.GA3411@jama.jama.net>
On 11/16/2012 12:07 AM, Martin Jansa wrote:
> On Wed, Aug 08, 2012 at 10:45:19AM -0700, Khem Raj wrote:
>> Hi
>>
>> Binutils 2.23 branch has started upstream. Given that toolchain
>> components require a lot of soak time, I have created the recipes
>> for binutils 2.23 and pushed it here
>>
>> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/binutils-2.23
>>
>> If you are using angstrom set
>>
>> ANGSTROM_BINUTILS_VERSION = "2.23" in local.conf after pulling that branch
>> for OE-Core it will work as it is
>>
>> Let me know if you see any errors.
>>
>> I will keep updating it until 2.23 release
>
> Now with danny released, can this be merged? Maybe updated to 2.23.1 too.
>
Apparently there is an issue with the SDK that is being worked on, once
that issue is resolved we will look into merging the updated version of
binutils.
Sau!
> Cheers,
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-11-16 19:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 17:45 binutils 2.23 call for testing the recipes Khem Raj
2012-08-09 13:10 ` Martin Jansa
2012-08-09 14:53 ` Khem Raj
2012-08-09 14:57 ` Martin Jansa
2012-08-11 8:04 ` Martin Jansa
2012-08-12 5:30 ` Khem Raj
2012-08-12 6:14 ` Martin Jansa
2012-08-16 10:36 ` Martin Jansa
2012-09-16 6:06 ` Martin Jansa
2012-09-17 1:22 ` Khem Raj
2012-11-16 8:07 ` Martin Jansa
2012-11-16 19:16 ` Saul Wold [this message]
2012-11-19 10:27 ` Enrico Scholz
2012-11-19 12:04 ` Marcin Juszkiewicz
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=50A69126.2070506@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@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.