Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: "André Draszik" <git@andred.net>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/4] uclibc: don't compile in mips16e mode
Date: Sat, 25 Jun 2016 09:18:06 -0700	[thread overview]
Message-ID: <576EAEBE.10108@gmail.com> (raw)
In-Reply-To: <1466765910-22989-2-git-send-email-git@andred.net>

Are these Krogoth worthy?

- armin

On 06/24/2016 03:58 AM, André Draszik wrote:
> From: André Draszik <adraszik@tycoint.com>
> 
> uClibc contains hand-written assembly which is not compatible with
> the MIPS16e mode.
> 
> Signed-off-by: André Draszik <adraszik@tycoint.com>
> ---
>  meta/recipes-core/uclibc/uclibc.inc | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/meta/recipes-core/uclibc/uclibc.inc b/meta/recipes-core/uclibc/uclibc.inc
> index 57f87fa..02cd8d1 100644
> --- a/meta/recipes-core/uclibc/uclibc.inc
> +++ b/meta/recipes-core/uclibc/uclibc.inc
> @@ -63,6 +63,10 @@ EXTRA_OEMAKE_task_do_package = "${OEMAKE_NO_CC}"
>  CFLAGS_remove_arm = "-fno-omit-frame-pointer"
>  UCLIBC_EXTRA_CFLAGS  = "${@oe_filter_out('(-I\S+|-i\S+)', '${CFLAGS}', d)}"
>  
> +# Doesn't compile in MIPS16e mode due to use of hand-written
> +# assembly
> +MIPS_INSTRUCTION_SET_pn-uclibc = "mips"
> +
>  configmangle = '/^KERNEL_HEADERS/d; \
>                  /^RUNTIME_PREFIX/d; \
>                  /^DEVEL_PREFIX/d; \
> 


  reply	other threads:[~2016-06-25 16:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 10:58 [PATCH 1/4] gmp: don't compile in mips16e mode André Draszik
2016-06-24 10:58 ` [PATCH 2/4] uclibc: " André Draszik
2016-06-25 16:18   ` akuster808 [this message]
2016-06-25 17:34     ` Khem Raj
2016-06-24 10:58 ` [PATCH 3/4] libffi: " André Draszik
2016-06-24 10:58 ` [PATCH 4/4] glib: disable valgrind support when compiling " André Draszik

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=576EAEBE.10108@gmail.com \
    --to=akuster808@gmail.com \
    --cc=git@andred.net \
    --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