From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: some rather obvious syntax errors just checked into oe-core
Date: Sun, 22 Jul 2012 15:05:26 +0100 [thread overview]
Message-ID: <1342965926.21788.77.camel@ted> (raw)
In-Reply-To: <alpine.DEB.2.02.1207220828260.17793@oneiric>
On Sun, 2012-07-22 at 08:31 -0400, Robert P. J. Day wrote:
> $ bitbake -c fetchall core-image-minimal
> Pseudo is not present but is required, building this first before the main build
> Loading cache: 100% |#######################################################################| ETA: 00:00:00
> Loaded 708 entries from dependency cache.
> ERROR: ParseError at /home/rpjday/oe/oe-core/meta/recipes-devtools/python/python-native_2.7.3.bb:23:
> unparsed line: 'EXTRA_OECONF_append " --bindir=${bindir}/${PN}"'
>
> there's a missing "=" here ^^^^^^^^^ in python-native_2.7.3.bb
Managed to cherry-pick a broken revision :/. Fixed, sorry about that.
Cheers,
Richard
prev parent reply other threads:[~2012-07-22 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 12:31 some rather obvious syntax errors just checked into oe-core Robert P. J. Day
2012-07-22 14:05 ` Richard Purdie [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=1342965926.21788.77.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox