From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@yoctoproject.org,
openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] Toolchain rework, call for testing
Date: Tue, 21 Aug 2012 20:28:13 +0200 [thread overview]
Message-ID: <20120821182813.GF3029@jama.jama.net> (raw)
In-Reply-To: <CAMKF1spWTYExCcvQ9Uqo-470Qxb2NTwB_xYHhU7RzFOuiYP_VA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
On Tue, Aug 21, 2012 at 10:15:47AM -0700, Khem Raj wrote:
> On Tue, Aug 21, 2012 at 5:18 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> >
> > Maybe it's because
> > http://git.openembedded.org/openembedded-core/commit/?id=30617bde61a3b0a0944b49a0c9fb7159dacbb19f
> > is missing PR bump and gcc wasn't rebuilt before eglibc upgrade (OEBasic not OEBasicHash here).
>
> yes seems so. I have stopped using OEBasic long ago, you should stop
> using it too.
I'm using OEBasicHash on one jenkins setup, but that one is still
building changes from 2 days ago.. (building 24/7.. )
> But feel free to send a PR bump patchlet.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2012-08-21 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 4:47 Toolchain rework, call for testing Khem Raj
2012-08-17 16:21 ` Christopher Larson
2012-08-21 3:35 ` Saul Wold
2012-08-21 4:35 ` Khem Raj
2012-08-21 11:55 ` Marcin Juszkiewicz
2012-08-21 12:00 ` Phil Blundell
2012-08-21 12:07 ` Martin Jansa
2012-08-21 12:23 ` Gary Thomas
2012-08-21 17:13 ` Khem Raj
2012-08-21 18:37 ` Khem Raj
2012-08-21 12:18 ` [yocto] " Martin Jansa
2012-08-21 17:15 ` Khem Raj
2012-08-21 18:28 ` Martin Jansa [this message]
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=20120821182813.GF3029@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox