From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13011] New: Incorrect selection of gcc version
Date: Wed, 17 Jun 2020 22:05:07 +0000 [thread overview]
Message-ID: <bug-13011-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13011
Bug ID: 13011
Summary: Incorrect selection of gcc version
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: blocker
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: vernon2gm at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
Hi:
I use buildroot External toolchain
$ make menuconfig
Toolchain --->
External toolchain gcc version (9.x) --->
gcc is ubuntu20.04 by `sudo apt install gcc` install, it's version is 9.3.0, so
gcc -dumpversion is 9
but toolchain/helpers.mk check_gcc_version function to display error
I fixed this bug, as follows:
diff --git a/toolchain/helpers.mk b/toolchain/helpers.mk
index 44d0c83d1e..7c7819f9a6 100644
--- a/toolchain/helpers.mk
+++ b/toolchain/helpers.mk
@@ -184,7 +184,7 @@ check_gcc_version = \
exit 0 ; \
fi; \
real_version=`$(1) -dumpversion` ; \
- if [[ ! "$${real_version}" =~ ^$${expected_version}\. ]] ; then \
+ if [[ ! "$${real_version}" =~ ^$${expected_version} ]] ; then \
printf "Incorrect selection of gcc version: expected %s.x, got
%s\n" \
"$${expected_version}" "$${real_version}" ; \
exit 1 ; \
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-06-17 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 22:05 bugzilla at busybox.net [this message]
2020-06-18 7:23 ` [Buildroot] [Bug 13011] Incorrect selection of gcc version bugzilla at busybox.net
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=bug-13011-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.