From: Kaz Kojima <kkojima@rr.iij4u.or.jp>
To: Anthony Green <green@moxielogic.com>
Cc: gcc-patches@gcc.gnu.org, libffi-discuss@sourceware.org
Subject: [patch RFA libffi SH] Fix configure error for sh4-unknown-linux-gnu
Date: Tue, 13 Jan 2015 05:38:00 -0000 [thread overview]
Message-ID: <20150113.143839.316693206.kkojima@rr.iij4u.or.jp> (raw)
Hi,
The attached patch is to fix libffi build failure for
sh4-unknown-linux-gnu. Without it, configure fails with:
configure: error: "libffi has not been ported to sh4-unknown-linux-gnu."
on that target. OK for trunk?
Regards,
kaz
--
2015-01-13 Kaz Kojima <kkojima@gcc.gnu.org>
* configure.host: Remove extra brackets for sh.
diff --git a/configure.host b/configure.host
index 90de638..4952345 100644
--- a/configure.host
+++ b/configure.host
@@ -194,7 +194,7 @@ case "${host}" in
SOURCES="ffi.c sysv.S"
;;
- sh-*-* | sh[[34]]*-*-*)
+ sh-*-* | sh[34]*-*-*)
TARGET=SH; TARGETDIR=sh
SOURCES="ffi.c sysv.S"
;;
next reply other threads:[~2015-01-13 5:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 5:38 Kaz Kojima [this message]
2015-01-13 15:21 ` Richard Henderson
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=20150113.143839.316693206.kkojima@rr.iij4u.or.jp \
--to=kkojima@rr.iij4u.or.jp \
--cc=gcc-patches@gcc.gnu.org \
--cc=green@moxielogic.com \
--cc=libffi-discuss@sourceware.org \
/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).