From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: [RFC]: Toolchain build sequence alteration.
Date: Fri, 25 Jul 2008 09:06:45 -0700 [thread overview]
Message-ID: <20080725160645.GB9454@gmail.com> (raw)
In-Reply-To: <20080725100127.GA4554@rhein.zuhause.netz>
On (25/07/08 12:01), Henning Heinold wrote:
> On Fri, Jul 25, 2008 at 12:33:04AM -0700, Khem Raj wrote:
> > On (24/07/08 18:18), Koen Kooi wrote:
> >
> > Thank you Koen and RP for testing it out and ACK'ing. I have committed
> > the big patch. Let me know of any fallouts and I will try to fix them.
> >
> > Happy hacking.
>
> Hi,
>
> I find the first strange think when using angstroem and uclibc with
> armoabi. TARGET_OS is configured at
>
> include/distro/angstrom-uclibc.conf
>
> with
> TARGET_OS_UC =
> "linux${@['-uclibc','-uclibcgnueabi'][bb.data.getVar('TARGET_ARCH',d,1)
> in ['arm', 'armeb'] and bb.data.getVar('MACHINE',d) not in
> ['collie','h3600', 'h3800', 'simpad', 'htcwallaby']]}"
>
> and
>
> TARGET_OS ?= "${@['${TARGET_OS_UC}',
> 'uclinux-uclibc'][bb.data.getVar('TARGET_ARCH',d) in ['bfin']]}"
>
> For some reason it dont set TARGET_OS and therefor the sanity checker
> bails out.
>
> For now I swtiched back to TARGET_OS = ..., as before and I am able to
> build packages again.
You can add this to your local.conf file. if you make it hard assignment
you wont be able to override it in local.conf for the architectures not
mentioned in this conditional.
Thanks
-Khem
>
> Bye,
>
> Henning
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2008-07-25 16:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 1:58 [RFC]: Toolchain build sequence alteration Khem Raj
2008-07-15 7:34 ` Henning Heinold
2008-07-16 8:10 ` Khem Raj
2008-07-16 8:46 ` Koen Kooi
2008-07-16 15:27 ` Khem Raj
2008-07-16 20:43 ` Leon Woestenberg
2008-07-17 8:43 ` Khem Raj
2008-07-22 0:28 ` Khem Raj
[not found] ` <20080720014112.GA13759@oberlord>
2008-07-23 9:04 ` Khem Raj
2008-07-24 9:10 ` Richard Purdie
2008-07-24 16:05 ` Richard Purdie
2008-07-24 16:18 ` Koen Kooi
2008-07-25 7:33 ` Khem Raj
2008-07-25 10:01 ` Henning Heinold
2008-07-25 16:06 ` Khem Raj [this message]
2008-07-28 6:27 ` SH7760 Problems Stefano Regno
2008-08-02 12:03 ` [RFC]: Toolchain build sequence alteration Koen Kooi
2008-08-02 15:14 ` Phil Blundell
2008-08-02 15:45 ` Koen Kooi
2008-08-03 2:47 ` Khem Raj
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=20080725160645.GB9454@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.