From: Lothar Felten <lothar.felten@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] beaglebone_qt5_defconfig: use gcc 5.x
Date: Fri, 11 Aug 2017 13:16:04 +0200 [thread overview]
Message-ID: <1502450164-3015-1-git-send-email-lothar.felten@gmail.com> (raw)
The linux 4.1 kernel does not compile with gcc 6.x.
The compiler version is now fixed to 5.x until a new kernel is used.
Signed-off-by: Lothar Felten <lothar.felten@gmail.com>
---
configs/beaglebone_qt5_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/beaglebone_qt5_defconfig b/configs/beaglebone_qt5_defconfig
index 4135f71..fb61bf5 100644
--- a/configs/beaglebone_qt5_defconfig
+++ b/configs/beaglebone_qt5_defconfig
@@ -3,6 +3,7 @@ BR2_cortex_a8=y
BR2_GLOBAL_PATCH_DIR="board/beaglebone/patches"
BR2_PACKAGE_HOST_LINUX_HEADERS_CUSTOM_4_1=y
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
+BR2_GCC_VERSION_5_X=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
BR2_TARGET_GENERIC_GETTY_PORT="ttyO0"
--
1.9.1
next reply other threads:[~2017-08-11 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 11:16 Lothar Felten [this message]
2017-08-11 13:32 ` [Buildroot] [PATCH 1/1] beaglebone_qt5_defconfig: use gcc 5.x Thomas Petazzoni
2018-05-27 20:10 ` Romain Naour
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=1502450164-3015-1-git-send-email-lothar.felten@gmail.com \
--to=lothar.felten@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox