All of lore.kernel.org
 help / color / mirror / Atom feed
From: wenzong fan <wenzong.fan@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] openssl: fix mips64 configure support
Date: Sat, 7 Nov 2015 15:23:55 +0800	[thread overview]
Message-ID: <563DA70B.8090409@windriver.com> (raw)
In-Reply-To: <CAMKF1spYkB4xA94TuVUkaX3g-U3+TmPnhDQMN+EzTgX1pMKZdQ@mail.gmail.com>

On 11/07/2015 03:09 PM, Khem Raj wrote:
> On Fri, Nov 6, 2015 at 11:07 PM, wenzong fan <wenzong.fan@windriver.com> wrote:
>> If target name is linux-mips64, set it as linux-mips to get it build with
>> mips(32) userspace.
>
> is it really building for mips32 ?
>
>

Yes, with this change, the "Configure" will pass '-mips2' to CFLAGS, 
otherwise it will pass '-mips3' which may cause build errors:

| Error: -mips3 conflicts with the other architecture options, which 
imply -mips64r2
| cryptlib.c:1:0: error: '-mips3' conflicts with the other architecture 
options, which specify a mips64r2 processor

I built it with a cav-octeon3 bsp.

Looks openssl doesn't work with mips64 userspace, I got this from git logs:

commit 858646c7bd11d1dad8c14e30f3fe6b4bd58a31b2
Author: Randy MacLeod <Randy.MacLeod@windriver.com>
Date:   Fri Dec 21 14:05:46 2012 -0500

     openssl: Add mips64 configure support.

     Add mips64 configure support but assume mips(32) userspace.

     (From OE-Core rev: 7d775b071b902ee0de6391b2c30d36e3003643e1)

     Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
     Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
     Signed-off-by: Saul Wold <sgw@linux.intel.com>
     Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

diff --git a/meta/recipes-connectivity/openssl/openssl.inc 
b/meta/recipes-connectivity/openssl/openssl.inc
index e1e7b65..af1922e 100644
--- a/meta/recipes-connectivity/openssl/openssl.inc
+++ b/meta/recipes-connectivity/openssl/openssl.inc
@@ -95,6 +95,9 @@ do_configure () {
         linux-mipsel)
                 target=debian-mipsel
                 ;;
+        linux-*-mips64)
+               target=linux-mips
+                ;;
         linux-powerpc)
                 target=linux-ppc
                 ;;

Thanks
Wenzong


      reply	other threads:[~2015-11-07  7:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-05  6:09 [PATCH] openssl: fix mips64 configure support wenzong.fan
2015-11-05 16:18 ` Khem Raj
2015-11-07  7:07   ` wenzong fan
2015-11-07  7:09     ` Khem Raj
2015-11-07  7:23       ` wenzong fan [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=563DA70B.8090409@windriver.com \
    --to=wenzong.fan@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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.