From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] eglibc-2.12: Fix build on powerpc/603e
Date: Thu, 22 Sep 2011 21:02:56 +0100 [thread overview]
Message-ID: <1316721783.28323.4.camel@ted> (raw)
In-Reply-To: <1316707046-24981-1-git-send-email-raj.khem@gmail.com>
On Thu, 2011-09-22 at 08:57 -0700, Khem Raj wrote:
> We pass --with-cpu to eglibc now. Which breaks
> the configure for cpus that it does not support
> We add support for ppc603e which gets 2.12
> building for qemuppc.
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> .../eglibc/eglibc-2.12/ppc-enable-603e-cpu.patch | 26 ++++++++++++++++++++
> meta/recipes-core/eglibc/eglibc_2.12.bb | 3 +-
> 2 files changed, 28 insertions(+), 1 deletions(-)
> create mode 100644 meta/recipes-core/eglibc/eglibc-2.12/ppc-enable-603e-cpu.patch
>
> diff --git a/meta/recipes-core/eglibc/eglibc-2.12/ppc-enable-603e-cpu.patch b/meta/recipes-core/eglibc/eglibc-2.12/ppc-enable-603e-cpu.patch
> new file mode 100644
> index 0000000..5c90e5b
> --- /dev/null
> +++ b/meta/recipes-core/eglibc/eglibc-2.12/ppc-enable-603e-cpu.patch
> @@ -0,0 +1,26 @@
> +We now pass --with-cpu option to eglibc this ends up with configure errors if we do
> +not pass a cpu which eglibc has support for in sysdeps
> +
> +| checking sysdep dirs... configure: error: The 603e subspecies of powerpc is not supported.
> +| + bbfatal 'oe_runconf failed'
> +| + echo 'ERROR: oe_runconf failed'
> +
> +We fix this by adding the 603e sub directories with Implies to generic
> +powerpc to overcome this error
> +
> +Upstream-Status: Inappropriate [OE config related]
> +
> +Signed-off-by: Khem Raj <raj.khem@gmail.com>
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-09-22 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 15:57 [PATCH] eglibc-2.12: Fix build on powerpc/603e Khem Raj
2011-09-22 20:02 ` 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=1316721783.28323.4.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