From: wenzong fan <wenzong.fan@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] openssl: fix mips64 configure support
Date: Sat, 7 Nov 2015 15:07:07 +0800 [thread overview]
Message-ID: <563DA31B.5080404@windriver.com> (raw)
In-Reply-To: <11B9075E-35C1-4101-8072-D44DCDF9A210@gmail.com>
On 11/06/2015 12:18 AM, Khem Raj wrote:
>
>> On Nov 4, 2015, at 10:09 PM, wenzong.fan@windriver.com wrote:
>>
>> From: Wenzong Fan <wenzong.fan@windriver.com>
>>
>> Match target name linux-mips64 as well, all mips64 targets will have
>> mips(32) userspace.
>
> this comment seems to be not relevant to the change
>
What about:
If target name is linux-mips64, set it as linux-mips to get it build
with mips(32) userspace.
Thanks
Wenzong
>>
>> Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
>> ---
>> meta/recipes-connectivity/openssl/openssl.inc | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-connectivity/openssl/openssl.inc b/meta/recipes-connectivity/openssl/openssl.inc
>> index 8af423f..b69cb4c 100644
>> --- a/meta/recipes-connectivity/openssl/openssl.inc
>> +++ b/meta/recipes-connectivity/openssl/openssl.inc
>> @@ -115,7 +115,7 @@ do_configure () {
>> linux-mipsel)
>> target=debian-mipsel
>> ;;
>> - linux-*-mips64)
>> + linux-*-mips64 | linux-mips64)
>> target=linux-mips
>> ;;
>> linux-microblaze*|linux-nios2*)
>> --
>> 1.9.1
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2015-11-07 7:07 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 [this message]
2015-11-07 7:09 ` Khem Raj
2015-11-07 7:23 ` wenzong fan
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=563DA31B.5080404@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.