From: Carlos Santos <casantos@datacom.ind.br>
To: newlib@sourceware.org
Cc: Bryan Hundven <bryanhundven@gmail.com>, Alexey Neyman <stilor@att.net>
Subject: [PATCH] libgloss/arm: fix dircovery of "eabihf" toolchains
Date: Thu, 13 Apr 2017 23:17:00 -0000 [thread overview]
Message-ID: <1492125457-26653-1-git-send-email-casantos@datacom.ind.br> (raw)
ARM EABI toolchains can optionally use the "hf" suffix to identify
hardware floating point support. Use the "*-*-eabi*" pattern to match
these toolchains.
Original patch by Bryan Hundven for the Crosstool-NG project. Improved
by Alexey Neyman.
Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
CC: Bryan Hundven <bryanhundven@gmail.com
CC: Alexey Neyman <stilor@att.net>
---
Tested on Crosstool-NG, building a toolchain for target
"armv7em-cortex_m4f-eabihf".
---
libgloss/arm/configure | 2 +-
libgloss/arm/configure.in | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/libgloss/arm/configure b/libgloss/arm/configure
index 93c2b27..1aed3a9 100644
--- a/libgloss/arm/configure
+++ b/libgloss/arm/configure
@@ -2531,7 +2531,7 @@ test "${CCASFLAGS+set}" = set || CCASFLAGS=$CFLAGS
case "${target}" in
- *-*-elf | *-*-eabi | *-*-tirtos*)
+ *-*-elf | *-*-eabi* | *-*-tirtos*)
objtype=elf-
;;
*-*-coff)
diff --git a/libgloss/arm/configure.in b/libgloss/arm/configure.in
index 39c15d7..5fa901d 100644
--- a/libgloss/arm/configure.in
+++ b/libgloss/arm/configure.in
@@ -49,7 +49,7 @@ AC_PROG_RANLIB
LIB_AM_PROG_AS
case "${target}" in
- *-*-elf | *-*-eabi | *-*-tirtos*)
+ *-*-elf | *-*-eabi* | *-*-tirtos*)
objtype=elf-
;;
*-*-coff)
--
2.7.4
next reply other threads:[~2017-04-13 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 23:17 Carlos Santos [this message]
2017-04-18 10:27 ` Corinna Vinschen
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=1492125457-26653-1-git-send-email-casantos@datacom.ind.br \
--to=casantos@datacom.ind.br \
--cc=bryanhundven@gmail.com \
--cc=newlib@sourceware.org \
--cc=stilor@att.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).