From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: gcc-patches@gcc.gnu.org
Cc: Joel Sherrill <joel.sherrill@oarcorp.com>
Subject: [PATCH 1/2] libada/Makefile.in: Add CFLAGS_FOR_TARGET to GNATLIBCFLAGS_FOR_C
Date: Tue, 12 Aug 2014 14:31:00 -0000 [thread overview]
Message-ID: <1407853881-11152-1-git-send-email-joel.sherrill@oarcorp.com> (raw)
This didn't get any comments earlier. Is it OK to comment?
Somewhere along the way, the Ada run-time Makefile's quit
honoring CFLAGS_FOR_TARGET. This just adds it back.
2014-08-12 Joel Sherrill <joel.sherrill@oarcorp.com>
* Makefile.in: Add CFLAGS_FOR_TARGET to GNATLIBCFLAGS_FOR_C.
---
libada/Makefile.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libada/Makefile.in b/libada/Makefile.in
index c307b99..93da740 100644
--- a/libada/Makefile.in
+++ b/libada/Makefile.in
@@ -60,7 +60,7 @@ CFLAGS=-g
PICFLAG = @PICFLAG@
GNATLIBFLAGS= -W -Wall -gnatpg -nostdinc
GNATLIBCFLAGS= -g -O2
-GNATLIBCFLAGS_FOR_C = -W -Wall $(GNATLIBCFLAGS) \
+GNATLIBCFLAGS_FOR_C = -W -Wall $(GNATLIBCFLAGS) $(CFLAGS_FOR_TARGET) \
-fexceptions -DIN_RTS @have_getipinfo@
host_subdir = @host_subdir@
--
1.9.3
next reply other threads:[~2014-08-12 14:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 14:31 Joel Sherrill [this message]
2014-08-12 14:31 ` [PATCH 2/2] gcc/ada/socket.c, gsocket.h: Add conditionals for RTEMS Joel Sherrill
2014-08-12 17:32 ` Arnaud Charlet
2014-08-12 17:33 ` [PATCH 1/2] libada/Makefile.in: Add CFLAGS_FOR_TARGET to GNATLIBCFLAGS_FOR_C Arnaud Charlet
2014-08-12 19:20 ` Joel Sherrill
2014-08-12 19:23 ` Arnaud Charlet
2014-08-12 19:29 ` Joel Sherrill
2014-08-12 19:30 ` Arnaud Charlet
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=1407853881-11152-1-git-send-email-joel.sherrill@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gcc-patches@gcc.gnu.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).