From: Roland Hieber <r.hieber@pengutronix.de>
To: distrokit@pengutronix.de
Cc: Roland Hieber <rohieb@rohieb.name>
Subject: [DistroKit] [PATCH 2/2] platform-rpi: toolchain version bump 2016.06 -> 2018.02
Date: Sun, 11 Mar 2018 21:19:10 +0100 [thread overview]
Message-ID: <20180311201910.10803-2-r.hieber@pengutronix.de> (raw)
In-Reply-To: <20180311201910.10803-1-r.hieber@pengutronix.de>
From: Roland Hieber <rohieb@rohieb.name>
Signed-off-by: Roland Hieber <rohieb@rohieb.name>
---
configs/platform-rpi/platformconfig | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/configs/platform-rpi/platformconfig b/configs/platform-rpi/platformconfig
index af37b3a..79b05c9 100644
--- a/configs/platform-rpi/platformconfig
+++ b/configs/platform-rpi/platformconfig
@@ -62,11 +62,11 @@ PTXCONF_SYSROOT_CROSS="${PTXDIST_PLATFORMDIR}/sysroot-cross"
#
# toolchain
#
-PTXCONF_CROSSCHAIN_VENDOR="OSELAS.Toolchain-2016.06"
-PTXCONF_CROSSCHAIN_CHECK="5.4.0"
+PTXCONF_CROSSCHAIN_VENDOR="OSELAS.Toolchain-2018.02"
+PTXCONF_CROSSCHAIN_CHECK="7.3.1"
PTXCONF_LIBC_GLIBC=y
# PTXCONF_LIBC_UCLIBC is not set
-PTXCONF_GLIBC_VERSION="2.23"
+PTXCONF_GLIBC_VERSION="2.27"
PTXCONF_GNU_TARGET="arm-1136jfs-linux-gnueabihf"
PTXCONF_COMPILER_PREFIX="${PTXCONF_GNU_TARGET}-"
PTXCONF_COMPILER_PREFIX_KERNEL="${PTXCONF_COMPILER_PREFIX}"
--
2.16.1
_______________________________________________
DistroKit mailing list
DistroKit@pengutronix.de
next prev parent reply other threads:[~2018-03-11 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 20:19 [DistroKit] [PATCH 1/2] platform-rpi: barebox: version bump 2017.11.0 -> 2018.03.0 Roland Hieber
2018-03-11 20:19 ` Roland Hieber [this message]
2018-03-15 14:18 ` [DistroKit] [PATCH 2/2] platform-rpi: toolchain version bump 2016.06 -> 2018.02 Robert Schwebel
2018-03-15 14:18 ` [DistroKit] [PATCH 1/2] platform-rpi: barebox: version bump 2017.11.0 -> 2018.03.0 Robert Schwebel
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=20180311201910.10803-2-r.hieber@pengutronix.de \
--to=r.hieber@pengutronix.de \
--cc=distrokit@pengutronix.de \
--cc=rohieb@rohieb.name \
/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