From: Peter Korsgaard <peter@korsgaard.com>
To: Nevo Hed <nhed+buildroot@starry.com>
Cc: Samuel Martin <s.martin49@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/nginx: override endianness
Date: Fri, 10 Sep 2021 11:59:14 +0200 [thread overview]
Message-ID: <87h7esbvkd.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210831202450.18238-2-nhed+buildroot@starry.com> (Nevo Hed's message of "Tue, 31 Aug 2021 16:24:50 -0400")
>>>>> "Nevo" == Nevo Hed <nhed+buildroot@starry.com> writes:
> Though several cross-compilation patches exist in buildroot's nginx
> package dir they do not seem to address endianness.
> The test program generated by the configure script compiles but fails
> to run (as it is built for another architecture) but the script does
> not distinguish between the failure to run the program and an
> indication of certain endianness. As such the fallback of big-endian
> is used. This setting then causes http2 headers (anything not in the
> static dictionary) to come out as undecipherable trash on 64bit
> targets (see ngx_http_v2_huff_encode_buf()).
> This commit includes a patch to the configure script to allow a
> `--force-endianness=big|little` flag as well as setting that flag in
> buildroot's package makefile.
> Signed-off-by: Nevo Hed <nhed+buildroot@starry.com>
Committed to 2021.02.x and 2021.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-10 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 20:24 [Buildroot] [PATCH v2 0/1] package/nginx: override endianness Nevo Hed
2021-08-31 20:24 ` [Buildroot] [PATCH 1/1] " Nevo Hed
2021-09-10 9:59 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-08-30 20:53 Nevo Hed
2021-08-31 11:11 ` Nevo Hed
2021-08-31 11:55 ` Baruch Siach
2021-08-31 13:45 ` Arnout Vandecappelle
2021-08-31 16:19 ` Nevo Hed
2021-08-31 16:39 ` Arnout Vandecappelle
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=87h7esbvkd.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=nhed+buildroot@starry.com \
--cc=s.martin49@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox