From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH 2/3] platforms: toolchain: bump default toolchain version
Date: Thu, 14 Nov 2019 17:01:15 +0100 [thread overview]
Message-ID: <20191114160116.20379-2-rhi@pengutronix.de> (raw)
In-Reply-To: <20191114160116.20379-1-rhi@pengutronix.de>
Prefer the currently released version for new platforms.
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
platforms/toolchain.in | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/platforms/toolchain.in b/platforms/toolchain.in
index c219fe29de25..026e4395c3ad 100644
--- a/platforms/toolchain.in
+++ b/platforms/toolchain.in
@@ -5,7 +5,7 @@ menu "toolchain "
config CROSSCHAIN_VENDOR
string
prompt "check for specific toolchain vendor"
- default "OSELAS.Toolchain-2016.06"
+ default "OSELAS.Toolchain-2019.09"
help
Add here an unique vendor string to ensure this project will
be build with the correct toolchain.
@@ -19,7 +19,7 @@ config CROSSCHAIN_VENDOR
config CROSSCHAIN_CHECK
string
prompt "check for specific gcc version"
- default "5.4.0"
+ default "9.2.1"
help
PTXdist calls your cross compiler with -dumpversion and
compares the output with this string. This should help
@@ -47,7 +47,7 @@ if LIBC_GLIBC
config GLIBC_VERSION
string
prompt "glibc version"
- default "2.23"
+ default "2.30"
help
Specify the glibc version this BSP shall be built with. This information
is used to guess the toolchain path if you use "ptxdist toolchain"
--
2.24.0
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-11-14 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 16:01 [ptxdist] [PATCH 1/3] ptxdist: _get_config_ptx: fix --force logic Roland Hieber
2019-11-14 16:01 ` Roland Hieber [this message]
2019-11-14 16:01 ` [ptxdist] [PATCH 3/3] ptxdist: add 'init', 'init-platform' commands to create new configs Roland Hieber
2019-11-15 14:09 ` Michael Olbrich
2019-11-15 14:30 ` Roland Hieber
2019-11-16 10:21 ` Michael Olbrich
2019-11-27 9:37 ` Roland Hieber
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=20191114160116.20379-2-rhi@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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