All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Aristov Maxim <aristovmax@gmail.com>
Cc: Aristov Maxim <m@ximilian.ru>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] uClibc: Resolve conflicting options when building for mips32
Date: Tue, 23 Oct 2012 11:44:56 -0700	[thread overview]
Message-ID: <5086E5A8.3010804@linux.intel.com> (raw)
In-Reply-To: <1350701827-10385-1-git-send-email-m@ximilian.ru>

On 10/19/2012 07:57 PM, Aristov Maxim wrote:
> Signed-off-by: Aristov Maxim <m@ximilian.ru>
> ---
>   .../uclibc/uclibc-0.9.33/mips/uClibc.machine           |   16 ----------------
>   .../recipes-core/uclibc/uclibc-git/mips/uClibc.machine |   16 ----------------
>   meta/recipes-core/uclibc/uclibc.inc                    |   10 ++++++++++
>   3 files changed, 10 insertions(+), 32 deletions(-)
>   delete mode 100644 meta/recipes-core/uclibc/uclibc-0.9.33/mips/uClibc.machine
>   delete mode 100644 meta/recipes-core/uclibc/uclibc-git/mips/uClibc.machine
>

Merged into OE-Core

Thanks
	Sua!

> diff --git a/meta/recipes-core/uclibc/uclibc-0.9.33/mips/uClibc.machine b/meta/recipes-core/uclibc/uclibc-0.9.33/mips/uClibc.machine
> deleted file mode 100644
> index 7d7ab3f..0000000
> --- a/meta/recipes-core/uclibc/uclibc-0.9.33/mips/uClibc.machine
> +++ /dev/null
> @@ -1,16 +0,0 @@
> -# in OE we use TARGET_CC_ARCH="-march=mips32" but by
> -# default uclibc uses mips1 ISA for o32 ABI which ends
> -# up with conflicting march options to gcc. Here we
> -# ask for MIPS32 ISA to match the OE defaults
> -
> -CONFIG_MIPS_ISA_MIPS32=y
> -
> -# Below options are exact copy of general
> -# uClibc.machine file
> -#
> -FORCE_OPTIONS_FOR_ARCH=y
> -ARCH_HAS_MMU=y
> -ARCH_USE_MMU=y
> -KERNEL_HEADERS="/usr/include"
> -HAVE_DOT_CONFIG=y
> -
> diff --git a/meta/recipes-core/uclibc/uclibc-git/mips/uClibc.machine b/meta/recipes-core/uclibc/uclibc-git/mips/uClibc.machine
> deleted file mode 100644
> index 7d7ab3f..0000000
> --- a/meta/recipes-core/uclibc/uclibc-git/mips/uClibc.machine
> +++ /dev/null
> @@ -1,16 +0,0 @@
> -# in OE we use TARGET_CC_ARCH="-march=mips32" but by
> -# default uclibc uses mips1 ISA for o32 ABI which ends
> -# up with conflicting march options to gcc. Here we
> -# ask for MIPS32 ISA to match the OE defaults
> -
> -CONFIG_MIPS_ISA_MIPS32=y
> -
> -# Below options are exact copy of general
> -# uClibc.machine file
> -#
> -FORCE_OPTIONS_FOR_ARCH=y
> -ARCH_HAS_MMU=y
> -ARCH_USE_MMU=y
> -KERNEL_HEADERS="/usr/include"
> -HAVE_DOT_CONFIG=y
> -
> diff --git a/meta/recipes-core/uclibc/uclibc.inc b/meta/recipes-core/uclibc/uclibc.inc
> index 6c98090..707b14e 100644
> --- a/meta/recipes-core/uclibc/uclibc.inc
> +++ b/meta/recipes-core/uclibc/uclibc.inc
> @@ -85,6 +85,15 @@ OE_DEL      := "${@features_to_uclibc_del(d)}"
>   python () {
>       if "${OE_DEL}":
>           d.setVar('configmangle_append', "${OE_DEL}" + "\n")
> +
> +    # by default uclibc uses mips1 ISA for o32 ABI
> +    # if we use TARGET_CC_ARCH="-march=mips32" we end up
> +    # with conflicting march options to gcc. Here we
> +    # ask for MIPS32 ISA to match the chosen arch
> +
> +    if "mips32" in d.getVar("TUNE_FEATURES",True):
> +        d.setVar('configmangle_append',
> +                 "/^### MIPS32_CHECK$/a\\\nCONFIG_MIPS_ISA_MIPS32=y\n\n")
>       if "${OE_FEATURES}":
>           d.setVar('configmangle_append',
>                      "/^### DISTRO FEATURES$/a\\\n%s\n\n" %
> @@ -133,6 +142,7 @@ do_configure() {
>           echo "### FPU" >>${S}/merged.config
>           echo "### ABI" >>${S}/merged.config
>           echo "### DISTRO FEATURES" >>${S}/merged.config
> +        echo "### MIPS32_CHECK" >>${S}/merged.config
>
>           # Mangle the resulting .config depending on OE variables
>           sed -i -e '${configmangle}' ${S}/merged.config
>



      reply	other threads:[~2012-10-23 18:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-20  2:57 [PATCH] uClibc: Resolve conflicting options when building for mips32 Aristov Maxim
2012-10-23 18:44 ` Saul Wold [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=5086E5A8.3010804@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=aristovmax@gmail.com \
    --cc=m@ximilian.ru \
    --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 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.