From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Ladislav Michl <oss-lists@triops.cz>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] OpenSSL for mips64
Date: Wed, 9 Apr 2025 08:32:25 +0200 [thread overview]
Message-ID: <Z_YUeVzgcq97w_HR@pengutronix.de> (raw)
In-Reply-To: <Z_WGG9x9C5i964K-@lenoch>
On Tue, Apr 08, 2025 at 10:24:59PM +0200, Ladislav Michl wrote:
> Building openssl for 64bit mips requires different config, which is
> easy to achieve:
> --- a/rules/openssl.make
> +++ b/rules/openssl.make
> @@ -45,11 +45,11 @@ OPENSSL_ARCH-$(PTXCONF_ARCH_ARM64) := debian-arm64
>
> ifdef PTXCONF_ENDIAN_LITTLE
> OPENSSL_ARCH-$(PTXCONF_ARCH_ARM) := debian-armel
> -OPENSSL_ARCH-$(PTXCONF_ARCH_MIPS) := debian-mipsel
> +OPENSSL_ARCH-$(PTXCONF_ARCH_MIPS) := debian-$(call ptx/ifdef,PTXCONF_ARCH_LP64,mips64el,mipsel)
> OPENSSL_ARCH-$(PTXCONF_ARCH_SH_SH3) := debian-sh3
> OPENSSL_ARCH-$(PTXCONF_ARCH_SH_SH4) := debian-sh4
> else
> -OPENSSL_ARCH-$(PTXCONF_ARCH_MIPS) := debian-mips
> +OPENSSL_ARCH-$(PTXCONF_ARCH_MIPS) := debian-$(call ptx/ifdef,PTXCONF_ARCH_LP64,mips64,mips)
> OPENSSL_ARCH-$(PTXCONF_ARCH_SH_SH3) := debian-sh3eb
> OPENSSL_ARCH-$(PTXCONF_ARCH_SH_SH4) := debian-sh4eb
> endif
>
> Harder part is where ARCH_LP64 to get from.
> - make it selectable
> - add ARCH_MIPS64
That one, probably similar to what we do for x86_64, so that ARCH_MIPS and
ARCH_MIPS64 are enabled at the same time.
Michael
> - ask used toolchain
> - ???
>
> Suggestions welcome,
> l.
>
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2025-04-09 6:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 20:24 Ladislav Michl
2025-04-09 6:32 ` Michael Olbrich [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=Z_YUeVzgcq97w_HR@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=oss-lists@triops.cz \
--cc=ptxdist@pengutronix.de \
/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