mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH v2 1/6] platform: bump default toolchain version
Date: Tue, 22 Sep 2020 11:28:56 +0200	[thread overview]
Message-ID: <20200922092901.30715-1-rhi@pengutronix.de> (raw)

Provide reasonably recent default values for new platforms.

Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
 v2: no changes

 platforms/toolchain.in | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/platforms/toolchain.in b/platforms/toolchain.in
index 026e4395c3ad..86e624329afd 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-2019.09"
+	default "OSELAS.Toolchain-2020.08"
 	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 "9.2.1"
+	default "10.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.30"
+	default "2.32"
 	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.28.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

             reply	other threads:[~2020-09-22  9:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-22  9:28 Roland Hieber [this message]
2020-09-22  9:28 ` [ptxdist] [PATCH v2 2/6] kernel, barebox: add descriptive help text for config options Roland Hieber
2020-10-14 10:30   ` [ptxdist] [APPLIED] " Michael Olbrich
2020-09-22  9:28 ` [ptxdist] [PATCH v2 3/6] image-root-tgz: add a help text Roland Hieber
2020-10-14 10:30   ` [ptxdist] [APPLIED] " Michael Olbrich
2020-09-22  9:28 ` [ptxdist] [PATCH v2 4/6] ptxdist: implement 'defconfig' commands for kconfig packages Roland Hieber
2020-09-28 13:34   ` Alexander Dahl
2020-10-09  8:52     ` Michael Olbrich
2020-09-22  9:29 ` [ptxdist] [PATCH v2 5/6] rules: move magic symbol into rules/ptxdist-version.in Roland Hieber
2020-10-14 10:30   ` [ptxdist] [APPLIED] " Michael Olbrich
2020-09-22  9:29 ` [ptxdist] [PATCH v2 6/6] ptxdist: add 'init' commands to create new configs Roland Hieber
2020-10-14 10:30 ` [ptxdist] [APPLIED] platform: bump default toolchain version Michael Olbrich

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=20200922092901.30715-1-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