From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 24/25] support/config-fragments/autobuild: use Bootlin toolchain for Xtensa uclibc
Date: Sat, 6 Feb 2021 17:12:29 +0100 [thread overview]
Message-ID: <20210206171229.6d045307@windsurf.home> (raw)
In-Reply-To: <cfj2fhx195.ln2@ID-313208.user.individual.net>
On Sat, 06 Feb 2021 14:51:08 +0100
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> > --- /dev/null
> > +++ b/support/config-fragments/autobuild/bootlin-xtensa-uclibc.config
> > @@ -0,0 +1,3 @@
> > +BR2_xtensa=y
> > +BR2_TOOLCHAIN_EXTERNAL=y
> > +BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_XTENSA_LX60_UCLIBC_STABLE=y
>
> Hi Thomas,
>
> this toolchains breaks building libmicrohttpd:
> http://autobuild.buildroot.net/?reason=libmicrohttpd-0.9.72
>
> "mhd_byteorder.h:161:2: error: #error Configure detected big endian byte
> order but headers specify different byte order"
>
> because gcc describes itself as little endian:
>
> $ output/host/bin/xtensa-linux-gcc -E -dD -xc /dev/null | grep BYTE
> #define __BYTE_ORDER__ __ORDER_LITTLE_ENDIAN__
>
> although the defconfig is big endian
>
> $ grep ENDIAN .config
> BR2_ENDIAN="BIG"
Thanks for reporting, I'll have a look at that!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-02-06 16:12 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 22:53 [Buildroot] [PATCH 00/25] Autobuilder toolchain updates Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 01/25] support/config-fragments/autobuild: use Bootlin toolchain for AArch64 glibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 02/25] support/config-fragments/autobuild: use Bootlin toolchain for ARCle HS38 uclibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 03/25] support/config-fragments/autobuild: use Bootlin toolchain for ARMv5 uclibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 04/25] support/config-fragments/autobuild: use Bootlin toolchain for ARMv7 glibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 05/25] support/config-fragments/autobuild: use Bootlin toolchain for ARMv7 musl Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 06/25] support/config-fragments/autobuild: use Bootlin toolchain for ARMv7-M uclibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 07/25] support/config-fragments/autobuild: use Bootlin toolchain for m68k 68040 uclibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 08/25] support/config-fragments/autobuild: use Bootlin toolchain for m68k 5208 uclibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 09/25] support/config-fragments/autobuild: use Bootlin toolchain for Microblaze EL uclibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 10/25] support/config-fragments/autobuild: use Bootlin toolchain for mipsel32r6 glibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 11/25] support/config-fragments/autobuild: use Bootlin toolchain for mipsel uclibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 12/25] support/config-fragments/autobuild: use Bootlin toolchain for NIOS2 glibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 13/25] support/config-fragments/autobuild: use Bootlin toolchain for OpenRISC uclibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 14/25] support/config-fragments/autobuild: use Bootlin toolchain for PowerPC64le Power8 glibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 15/25] support/config-fragments/autobuild: use Bootlin toolchain for PowerPC e500mc uclibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 16/25] support/config-fragments/autobuild: use Bootlin toolchain for RISC-V 32 glibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 17/25] support/config-fragments/autobuild: use Bootlin toolchain for RISC-V 64 glibc Thomas Petazzoni
2021-02-03 21:24 ` Yann E. MORIN
2021-02-04 9:20 ` Thomas Petazzoni
2021-02-05 8:54 ` Yann E. MORIN
2021-02-02 22:53 ` [Buildroot] [PATCH 18/25] support/config-fragments/autobuild: use Bootlin toolchain for RISC-V 64 musl Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 19/25] support/config-fragments/autobuild: use Bootlin toolchain for SH4 uclibc Thomas Petazzoni
2021-02-03 21:27 ` Yann E. MORIN
2021-02-04 9:22 ` Thomas Petazzoni
2021-02-05 8:57 ` Yann E. MORIN
2021-02-02 22:53 ` [Buildroot] [PATCH 20/25] support/config-fragments/autobuild: use Bootlin toolchain for SPARC uclibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 21/25] support/config-fragments/autobuild: use Bootlin toolchain for SPARC64 glibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 22/25] support/config-fragments/autobuild: use Bootlin toolchain for x86-64 uclibc Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 23/25] support/config-fragments/autobuild: use Bootlin toolchain for x86-64 musl Thomas Petazzoni
2021-02-02 22:53 ` [Buildroot] [PATCH 24/25] support/config-fragments/autobuild: use Bootlin toolchain for Xtensa uclibc Thomas Petazzoni
2021-02-03 21:36 ` Yann E. MORIN
2021-02-06 13:51 ` Bernd Kuhls
2021-02-06 16:12 ` Thomas Petazzoni [this message]
2021-02-02 22:53 ` [Buildroot] [PATCH 25/25] support/config-fragments/autobuild: update Buildroot toolchains to 2020.11.2 Thomas Petazzoni
2021-02-03 21:49 ` [Buildroot] [PATCH 00/25] Autobuilder toolchain updates Yann E. MORIN
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=20210206171229.6d045307@windsurf.home \
--to=thomas.petazzoni@bootlin.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