From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] tbb: add 4.1 20130116 version (4.1 update 2)
Date: Fri, 29 Mar 2013 13:21:56 +0100 [thread overview]
Message-ID: <20130329122156.GE11120@jama> (raw)
In-Reply-To: <51514A23.3080109@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
On Tue, Mar 26, 2013 at 08:11:31AM +0100, Marcin Juszkiewicz wrote:
> W dniu 26.03.2013 06:59, Khem Raj pisze:
> > On Mar 25, 2013, at 2:20 AM, Marcin Juszkiewicz
>
> >> +do_compile() { + oe_runmake compiler=gcc arch=${HOST_ARCH}
> >> runtime=cc4.7_libc2.17_kernel3.8 tbb tbbmalloc +}
>
> > hmmm do you have to encode the tools versions like that, say in
> > future we move to gcc 4.8 or kernel 3.9 will this need adjusting too?
>
> If runtime is not defined it is created based on host system so can be
> totally wrong. From quick look at makefiles there is only compiler part
> checked for "cc3" or "cc4" - to add some arguments to flags.
>
> New version sent.
Applied, thanks!
Hopefully in right (last) revision.
Would be great if you can update patchwork status and use PATCHvN for
next patches.
memcached/libmemcached are still pending (unresolved review comments
afaik).
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2013-03-29 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 9:20 [PATCH] tbb: add 4.1 20130116 version (4.1 update 2) Marcin Juszkiewicz
2013-03-26 5:59 ` Khem Raj
2013-03-26 7:11 ` [meta-oe][PATCH] " Marcin Juszkiewicz
2013-03-26 7:11 ` [PATCH] " Marcin Juszkiewicz
2013-03-29 12:21 ` 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=20130329122156.GE11120@jama \
--to=martin.jansa@gmail.com \
--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.