From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-01
Date: Wed, 2 Mar 2016 16:04:23 +0100 [thread overview]
Message-ID: <20160302160423.0143a79b@free-electrons.com> (raw)
In-Reply-To: <CANCHnQros_GrNhEnk74UG6Q8NiwO9ZvmELezDrMjwzwwv4dCzw@mail.gmail.com>
Hello,
On Wed, 2 Mar 2016 15:24:29 +0100, Jeroen Roovers wrote:
> I am curious about nginx in particular since I found a bug in its
> magnificent configuration system today (which I didn't exactly fix but
> worked around).
>
> Using GCC 4.9.3 I found last year that nginx compiled fine but dropped
> the response header returned by its proxies. I didn't know back then
> that nginx was to blame, but that's beside the matter.
> The gist is that it returned the remainder of the headers to the HTTP client.
>
> On 2 March 2016 at 08:30, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>
> > sparc | nginx-1.8.1 | NOK | http://autobuild.buildroot.net/results/9dc9e7d85a618e5e6fd9b892ba591fc95edd413a/
>
> I checked the log and indeed it correctly says:
>
> checking for system byte ordering ... big endian
>
> Note that this is a compile test on the host, which is a punishable
> offense in forward-thinking nations.
This clearly cannot be a run test on the host, because the host in
question is a x86-64 machine, which is little endian. So if the test
was actually looking at the host endianness, it should have concluded
"little endian".
However, one possibility is that we pass ac_cv_c_bigendian in the
environment of configure scripts, which might have been taken into
account by nginx configure script.
See package/Makefile.in in Buildroot:
ifeq ($(BR2_ENDIAN),"BIG")
BR2_AC_CV_C_BIGENDIAN = ac_cv_c_bigendian=yes
else
BR2_AC_CV_C_BIGENDIAN = ac_cv_c_bigendian=no
endif
> This is probably something that nginx developers should fix (perhaps
> by using a standardised configuration system?) but why I turn to the
> list is to ask if the autobuild logs return "big endian" for all
> platforms, and to suggest that perhaps this should be flagged somehow.
I'm not sure what you're flagging here. The configure script seems to
properly detect that SPARC is big endian, which looks alright.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-03-02 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-03-01 Thomas Petazzoni
2016-03-02 14:24 ` Jeroen Roovers
2016-03-02 14:26 ` Jeroen Roovers
2016-03-02 15:04 ` Thomas Petazzoni [this message]
2016-03-02 15:18 ` Peter Korsgaard
2016-03-02 15:21 ` Thomas Petazzoni
2016-03-02 15:25 ` Peter Korsgaard
2016-03-02 15:29 ` Jeroen Roovers
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=20160302160423.0143a79b@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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