From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 1/2] espeak: Use SITEINFO_ENDIANESS instead of SITEINFO_ENDIANNESS
Date: Tue, 26 Jul 2011 06:57:24 +0200 [thread overview]
Message-ID: <j0lhfk$s8o$1@dough.gmane.org> (raw)
In-Reply-To: <1311653193-29753-1-git-send-email-raj.khem@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 26-07-11 06:06, Khem Raj schreef:
> This spelling difference existed when siteinfo was in two places
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com> --- meta-oe/recipes-support/espeak/espeak_1.37.bb | 6 ++++-- 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/meta-oe/recipes-support/espeak/espeak_1.37.bb b/meta-oe/recipes-support/espeak/espeak_1.37.bb index 6cc4cd4..5f9fcc1 100644 --- a/meta-oe/recipes-support/espeak/espeak_1.37.bb +++ b/meta-oe/recipes-support/espeak/espeak_1.37.bb @@ -1,12 +1,14 @@ require espeak.inc inherit siteinfo
>
> -EXTRA_PHONEMES = '${@base_contains("SITEINFO_ENDIANNESS", "be", "espeak-data (= ${PV})", "", d)}' +EXTRA_PHONEMES = '${@base_contains("SITEINFO_ENDIANESS", "be", "espeak-data (= ${PV})", "", d)}'
The double N is the right spelling, so the oe-core class should be fixed instead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFOLkk0MkyGM64RGpERAnRYAKCRBX66mOL2iKwLICDQZD+aBO7hlACeJwYs
1n6vb7pwzBfZUK/mG3v2r3c=
=XeWv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-07-26 5:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 4:06 [meta-oe][PATCH 1/2] espeak: Use SITEINFO_ENDIANESS instead of SITEINFO_ENDIANNESS Khem Raj
2011-07-26 4:06 ` [meta-oe][PATCH 2/2] openssl: " Khem Raj
2011-07-26 4:57 ` Koen Kooi [this message]
2011-07-26 5:11 ` [meta-oe][PATCH 1/2] espeak: " 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='j0lhfk$s8o$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--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.