From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-05
Date: Mon, 6 May 2019 08:57:20 +0200 [thread overview]
Message-ID: <20190506085720.6db369b2@windsurf> (raw)
In-Reply-To: <20190506063546.hp5272fyzyt2zshw@sapphire.tkos.co.il>
Hello Baruch,
On Mon, 6 May 2019 09:35:46 +0300
Baruch Siach <baruch@tkos.co.il> wrote:
> Hi Thomas,
>
> On Mon, May 06, 2019 at 06:00:39AM -0000, Thomas Petazzoni wrote:
> > Detail of failures
> > ------------------
> >
> > nds32le | 18xx-ti-utils-R8.7_SP3 | NOK | http://autobuild.buildroot.net/results/3c93cfac81f15f4c18eb7ad578ad86bb7bcf1c12 |
>
> glibc does not work well with BR2_STATIC_LIBS. The combination of
> BR2_STATIC_LIBS with glibc configuration seems to only happen in builds for
> nds32le. Why is that?
Because:
diff --git a/toolchain/toolchain-external/toolchain-external-andes-nds32/Config.in b/toolchain/toolchain-external/toolchain-external-andes-nds32/Config.in
index e2fe63677d..2596fc3c8b 100644
--- a/toolchain/toolchain-external/toolchain-external-andes-nds32/Config.in
+++ b/toolchain/toolchain-external/toolchain-external-andes-nds32/Config.in
@@ -1,6 +1,7 @@
config BR2_TOOLCHAIN_EXTERNAL_ANDES_NDS32
bool "Andes nds32"
depends on BR2_nds32
+ depends on !BR2_STATIC_LIBS
select BR2_TOOLCHAIN_GCC_AT_LEAST_8
select BR2_TOOLCHAIN_EXTERNAL_GLIBC
select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_17
is missing.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-06 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2019-05-05 Thomas Petazzoni
2019-05-06 6:35 ` Baruch Siach
2019-05-06 6:57 ` Thomas Petazzoni [this message]
2019-05-06 20:35 ` Arnout Vandecappelle
2019-05-06 20:46 ` 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=20190506085720.6db369b2@windsurf \
--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