From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: build exception in sgmlspl-native
Date: Fri, 09 Oct 2009 14:50:05 +0200 [thread overview]
Message-ID: <4ACF317D.7060808@dresearch.de> (raw)
In-Reply-To: <4ACEFD4C.6060606@dresearch.de>
Steffen Sledz wrote:
> 'bitbake sgmlspl-native' fails in dev-branch (with last commit
> b696acdd7296726efce684e3434f6a6445ddd992) with this exception:
>
> ERROR: Error in executing:
> /home/DRESEARCH/sledz/work/openembedded/recipes/sgmlspl/sgmlspl-native_1.03ii.bb
> ERROR: Exception:<type 'exceptions.KeyError'> Message:'linux'
>
> For details see attached log. Could this be a linux vs. linux-gnu
> related problem?
I've done some tests and the build was definitly broken by
commit d685ab28a425740b4d6c98abb1423d7904240724
Author: Khem Raj <raj.khem@gmail.com>
Date: Wed Oct 7 12:39:04 2009 -0700
insane.bbclass: Use linux-gnu for TARGET_OS
* Add linux-uclibcspe
Can you please have a look at this.
Thx,
Steffen
next prev parent reply other threads:[~2009-10-09 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 9:07 build exception in sgmlspl-native Steffen Sledz
2009-10-09 12:50 ` Steffen Sledz [this message]
2009-10-09 13:13 ` Eric Bénard
2009-10-09 17:40 ` 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=4ACF317D.7060808@dresearch.de \
--to=sledz@dresearch.de \
--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.