From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/7] support/testing: test_glxinfo: remove BR2_TOOLCHAIN_EXTERNAL_LOCALE
Date: Mon, 6 Apr 2020 01:04:10 +0200 [thread overview]
Message-ID: <20200405230414.416403-3-romain.naour@gmail.com> (raw)
In-Reply-To: <20200405230414.416403-1-romain.naour@gmail.com>
The BR2_TOOLCHAIN_EXTERNAL_LOCALE is only defined for uClibc based
custom external toolchains.
The test_glxinfo is using a glibc toolchain, so the
"# BR2_TOOLCHAIN_EXTERNAL_LOCALE is not set" line disapear from
the generated dot config (.config) leading to an error due to
a new check in the testsuite infra.
There is the same problem with:
BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG=y
BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS=y
BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_NPTL=y
Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
support/testing/tests/package/test_glxinfo.py | 4 ----
1 file changed, 4 deletions(-)
diff --git a/support/testing/tests/package/test_glxinfo.py b/support/testing/tests/package/test_glxinfo.py
index a9df6ddf6f..f37236d161 100644
--- a/support/testing/tests/package/test_glxinfo.py
+++ b/support/testing/tests/package/test_glxinfo.py
@@ -15,12 +15,8 @@ class TestGlxinfo(infra.basetest.BRTest):
BR2_TOOLCHAIN_EXTERNAL_URL="http://toolchains.bootlin.com/downloads/releases/toolchains/x86-core2/tarballs/x86-core2--glibc--bleeding-edge-2018.11-1.tar.bz2"
BR2_TOOLCHAIN_EXTERNAL_GCC_8=y
BR2_TOOLCHAIN_EXTERNAL_HEADERS_4_14=y
- # BR2_TOOLCHAIN_EXTERNAL_LOCALE is not set
BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_TOOLCHAIN_EXTERNAL_HAS_SSP=y
- BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG=y
- BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS=y
- BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_NPTL=y
BR2_TOOLCHAIN_EXTERNAL_CUSTOM_GLIBC=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_VERSION=y
--
2.25.1
next prev parent reply other threads:[~2020-04-05 23:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 23:04 [Buildroot] [PATCH 1/7] support/testing: test_syslinux: fix flake8 errors Romain Naour
2020-04-05 23:04 ` [Buildroot] [PATCH 2/7] support/testing: test_syslinux: remove BR2_TOOLCHAIN_EXTERNAL_LOCALE Romain Naour
2020-04-05 23:04 ` Romain Naour [this message]
2020-04-05 23:04 ` [Buildroot] [PATCH 4/7] support/testing: test_tmux: remove BR2_GENERATE_LOCALE Romain Naour
2020-04-05 23:04 ` [Buildroot] [PATCH 5/7] support/testing: test_lxc: use ARM arm external toolchain Romain Naour
2020-04-05 23:04 ` [Buildroot] [PATCH 6/7] support/testing: don't use TestPythonPackageBase.config and linaro toolchain Romain Naour
2020-04-06 20:19 ` Thomas Petazzoni
2020-04-05 23:04 ` [Buildroot] [PATCH 7/7] support/testing: check if the defconfig provided for testing is valid Romain Naour
2020-04-06 20:17 ` [Buildroot] [PATCH 1/7] support/testing: test_syslinux: fix flake8 errors 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=20200405230414.416403-3-romain.naour@gmail.com \
--to=romain.naour@gmail.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 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.