From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2 2/5] bitbake.conf: remove TARGET_ARCH from in SDKPATH
Date: Thu, 01 Mar 2012 19:59:53 +0000 [thread overview]
Message-ID: <1330631993.12133.11.camel@ted> (raw)
In-Reply-To: <20120301182546.GK3831@jama.jama.net>
On Thu, 2012-03-01 at 19:25 +0100, Martin Jansa wrote:
> On Thu, Mar 01, 2012 at 10:40:52AM +0100, Martin Jansa wrote:
> > On Thu, Mar 01, 2012 at 01:23:29AM -0800, Khem Raj wrote:
> > > On 02/25/2012 11:49 PM, Martin Jansa wrote:
> > > > +SDK_NAME_PREFIX = "oecore"
> > >
> > > should this be weak assignment
> >
> > Yeah, probably could be (I'm not overwritting this from my distro conf
> > so I haven't tried), but SDK_NAME assignment also wasn't weak and distros
> > were overwritting it.
> >
> > Someone with custom SDK_NAME(_PREFIX) please try and send patch.
>
> And we should change TARGET_ARCH in SDK_NAME to
> PACKAGE_ARCH or TUNE_PKGARCH
>
> because meta-toolchain-gmae for armv7a ends in
> oecore-i686-arm-toolchain-gmae-20120229.tar.bz2
> and for armv4t with similar name (I was lucky that it took more then day to
> build)
> oecore-i686-arm-toolchain-gmae-20120301.tar.bz2
Agreed...
Cheers,
Richard
next prev parent reply other threads:[~2012-03-01 20:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 7:48 [PATCHv2 0/5] Pending patches Martin Jansa
2012-02-26 7:49 ` [PATCHv2 1/5] bitbake.conf: use weak assignment for BB_CONSOLELOG Martin Jansa
2012-02-26 7:49 ` [PATCHv2 2/5] bitbake.conf: remove TARGET_ARCH from in SDKPATH Martin Jansa
2012-03-01 9:23 ` Khem Raj
2012-03-01 9:40 ` Martin Jansa
2012-03-01 18:25 ` Martin Jansa
2012-03-01 19:59 ` Richard Purdie [this message]
2012-03-09 6:48 ` [PATCH] bitbake.conf: use PACKAGE_ARCH instead of TARGET_ARCH in SDK_NAME Martin Jansa
2012-03-09 16:32 ` McClintock Matthew-B29882
2012-03-09 16:33 ` McClintock Matthew-B29882
2012-03-09 17:00 ` Martin Jansa
2012-03-09 17:06 ` McClintock Matthew-B29882
2012-03-15 7:23 ` [PATCHv2] bitbake.conf: use TUNE_PKGARCH " Martin Jansa
2012-04-27 20:49 ` Saul Wold
2012-02-26 7:49 ` [PATCHv2 3/5] gdb-cross-canadian: build gdb with python support Martin Jansa
2012-02-26 7:49 ` [PATCHv2 4/5] sstatesig: add SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS option to exclude well defined recipe->dependency Martin Jansa
2012-02-26 7:49 ` [PATCHv2 5/5] layer.conf: add keymaps to SIGGEN_EXCLUDERECIPES_ABISAFE Martin Jansa
2012-02-26 11:01 ` [PATCHv2 0/5] Pending patches Richard Purdie
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=1330631993.12133.11.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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.