From: Eric Le Bihan <eric.le.bihan.dev@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-03-18
Date: Sun, 19 Mar 2017 15:44:11 +0100 [thread overview]
Message-ID: <20170319144411.GA9040@itchy> (raw)
In-Reply-To: <20170319072840.949DB2077A@mail.free-electrons.com>
Hi!
On 17-03-19 08:28:40, Thomas Petazzoni wrote:
>
> m68k | host-skalibs-2.4.0.2 | NOK | http://autobuild.buildroot.net/results/c2e8e1180571976b412cbba729c45a3698aea0b2 |
This one is puzzling. I could not reproduce it on my build machine
(Fedora 25, gcc 6.3.1).
The build of the host variant of skalibs fails at configuration time as
follow:
```
Checking whether system has timer_create()...
... yes, with -lrt
Checking system endianness...
./configure: unable to determine endianness
```
At this step, ./configure tries to compile two programs to determine
endianness (src/sysdeps/trybigendian.c and src/sysdeps/trylittleendian.c).
Both test some compiler macros related to endianness. Example, for big
endian:
```
#if defined(__BYTE_ORDER) && (__BYTE_ORDER == __BIG_ENDIAN) ||? \
? defined(__BYTE_ORDER__) && (__BYTE_ORDER__ ==
__ORDER_BIG_ENDIAN__) || \
? defined(__BIG_ENDIAN) ||? ? ? ? \
? defined(__ARMEB__) ||? ? ? ? ? \
? defined(__THUMBEB__) ||? ? ? ? \
? defined(__AARCH64EB__) ||? ? ? ? \
? defined(_MIPSEB) || defined(__MIPSEB) || defined(__MIPSEB__)
#define YEAH
#else
#error "not big endian"
#endif
```
So the failure means that both programs failed to compile. Which
version of GCC is used on the autobuild machine?
Best regards,
--
ELB
next prev parent reply other threads:[~2017-03-19 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-03-18 Thomas Petazzoni
2017-03-19 14:44 ` Eric Le Bihan [this message]
2017-03-19 15:00 ` Thomas Petazzoni
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=20170319144411.GA9040@itchy \
--to=eric.le.bihan.dev@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.