From: Khem Raj <raj.khem@gmail.com>
To: git@andred.net
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] musl: don't compile in mips16e mode
Date: Wed, 20 Jul 2016 20:22:21 -0700 [thread overview]
Message-ID: <76D6B136-02D8-404A-8AB1-3F236ABAB58D@gmail.com> (raw)
In-Reply-To: <1469071188-26218-1-git-send-email-git@andred.net>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
> On Jul 20, 2016, at 8:19 PM, git@andred.net wrote:
>
> From: André Draszik <adraszik@tycoint.com>
>
> musl contains hand-written assembly which is not compatible with
> the MIPS16e mode.
>
> Signed-off-by: André Draszik <adraszik@tycoint.com>
> ---
> meta/recipes-core/musl/musl.inc | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-core/musl/musl.inc b/meta/recipes-core/musl/musl.inc
> index 5e6cd01..276b00f 100644
> --- a/meta/recipes-core/musl/musl.inc
> +++ b/meta/recipes-core/musl/musl.inc
> @@ -24,3 +24,6 @@ FILES_SOLIBSDEV = ""
> FILES_${PN} += "${libdir}/lib*${SOLIBSDEV}"
> INSANE_SKIP_${PN} = "dev-so"
>
> +# Doesn't compile in MIPS16e mode due to use of hand-written
> +# assembly
> +MIPS_INSTRUCTION_SET = “mips"
Looks ok. However, does it make sense to have it compiled with mips ISA for a mips16e
part ? will it work in all cases or only certain SOCs
> --
> 2.8.1
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-07-21 3:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 3:19 [PATCH] musl: don't compile in mips16e mode git
2016-07-21 3:22 ` Khem Raj [this message]
2016-07-21 10:16 ` André Draszik
2016-07-21 13:46 ` 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=76D6B136-02D8-404A-8AB1-3F236ABAB58D@gmail.com \
--to=raj.khem@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 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.