From: Michael Olbrich <m.olbrich@pengutronix.de>
To: Ladislav Michl <oss-lists@triops.cz>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] openssl: fix configuration for mips64
Date: Fri, 9 May 2025 10:37:49 +0200 [thread overview]
Message-ID: <aB2-3ZcCv5HLR8zG@pengutronix.de> (raw)
In-Reply-To: <aBnwkfqsKkF4QOq9@lenoch>
On Tue, May 06, 2025 at 01:20:49PM +0200, Ladislav Michl wrote:
> From: Ladislav Michl <ladis@triops.cz>
>
> Signed-off-by: Ladislav Michl <ladis@triops.cz>
> ---
> rules/openssl.make | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/rules/openssl.make b/rules/openssl.make
> index f2e985b58..2cdaf5259 100644
> --- 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)
PTXCONF_ARCH_MIPS in combination with PTXCONF_ARCH_LP64 is currently not
possible in PTXdist upstream. I assume you have local changes to
platforms/architecture.in. Can you send those as well?
Michael
> 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
> --
> 2.39.5
>
>
>
--
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-05-09 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 11:20 Ladislav Michl
2025-05-09 8:37 ` 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=aB2-3ZcCv5HLR8zG@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