public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/marxin/heads/cc-renaming)] Manual changes. Date: Mon, 10 Jan 2022 10:22:35 +0000 (GMT) [thread overview] Message-ID: <20220110102235.73EE338930DE@sourceware.org> (raw) https://gcc.gnu.org/g:8f7e88d6ee20951f7f73fa604eae17804bde7853 commit 8f7e88d6ee20951f7f73fa604eae17804bde7853 Author: Martin Liska <mliska@suse.cz> Date: Mon Jan 10 11:22:24 2022 +0100 Manual changes. Diff: --- gcc/ada/gcc-interface/Make-lang.in | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/ada/gcc-interface/Make-lang.in b/gcc/ada/gcc-interface/Make-lang.in index c6d8134b12b..59707188ae9 100644 --- a/gcc/ada/gcc-interface/Make-lang.in +++ b/gcc/ada/gcc-interface/Make-lang.in @@ -121,13 +121,13 @@ ADA_TOOLS=gnatbind gnatchop gnat gnatkr gnatlink gnatls gnatmake \ # Say how to compile Ada programs. .SUFFIXES: .ada .adb .ads -# FIXME: need to add $(ADA_CFLAGS) to .c.o suffix rule +# FIXME: need to add $(ADA_CFLAGS) to .cc.o suffix rule # Use mildly strict warnings for this front end and add special flags. ada-warn = $(ADA_CFLAGS) $(filter-out -pedantic, $(STRICT_WARN)) # Unresolved warnings in specific files. ada/adaint.o-warn = -Wno-error -ada/%.o: ada/gcc-interface/%.c +ada/%.o: ada/gcc-interface/%.cc $(COMPILE) $< $(POSTCOMPILE) @@ -797,7 +797,7 @@ ada.srcextra: ada.srcman: ada.tags: force - cd $(srcdir)/ada && $(ETAGS) -o TAGS.sub *.c *.h *.ads *.adb && \ + cd $(srcdir)/ada && $(ETAGS) -o TAGS.sub *.cc *.h *.ads *.adb && \ $(ETAGS) --include TAGS.sub --include ../TAGS.sub
next reply other threads:[~2022-01-10 10:22 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-10 10:22 Martin Liska [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-01-11 12:47 Martin Liska 2022-01-11 10:32 Martin Liska 2022-01-11 9:50 Martin Liska 2022-01-10 19:52 Martin Liska 2022-01-10 10:14 Martin Liska
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=20220110102235.73EE338930DE@sourceware.org \ --to=marxin@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).