From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Fabian Pfitzner <f.pfitzner@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] nginx: re-add force-endianness option
Date: Sat, 24 Oct 2026 09:16:25 +0200 [thread overview]
Message-ID: <20261024071625.2486066-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20261013095542.670546-1-f.pfitzner@pengutronix.de>
Thanks, applied as 41580de32c007f38d61cb263cece1d84f810eb8a.
Michael
[sent from post-receive hook]
On Sat, 24 Oct 2026 09:16:25 +0200, Fabian Pfitzner <f.pfitzner@pengutronix.de> wrote:
> During the nginx update [1] the option `--force-endianness` was
> accidentally removed. There is still the downstream patch that
> implements this option [2], thus re-add this option to the rule file.
>
> [1] f1ea787fb ("nginx: version bump 1.24.0 -> 1.29.1")
> [2] patches/nginx-1.29.1/0010-Allow-forcing-of-endianness-for-cross-compilation.patch
>
> Signed-off-by: Fabian Pfitzner <f.pfitzner@pengutronix.de>
> Message-Id: <20261013095542.670546-1-f.pfitzner@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/nginx.make b/rules/nginx.make
> index 9d9a479729ab..d9d40b7ca22e 100644
> --- a/rules/nginx.make
> +++ b/rules/nginx.make
> @@ -64,6 +64,7 @@ NGINX_CONF_OPT := \
> --lock-path=/var/lock/nginx.lock \
> --user=www \
> --group=www \
> + --force-endianness=$(call ptx/ifdef,PTXCONF_ENDIAN_LITTLE,little,big) \
> $(call ptx/ifdef, PTXCONF_NGINX_THREADS,--with-threads) \
> $(call ptx/ifdef, PTXCONF_NGINX_HTTP_SSL_MODULE,--with-http_ssl_module) \
> $(call ptx/ifdef, PTXCONF_NGINX_HTTP_V2_MODULE,--with-http_v2_module) \
prev parent reply other threads:[~2026-10-24 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 9:55 [ptxdist] [PATCH] " Fabian Pfitzner
2026-10-24 7:16 ` 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=20261024071625.2486066-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=f.pfitzner@pengutronix.de \
--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