From: Jason Merrill <jason@cygnus.com>
To: wilson@cygnus.com, egcs@cygnus.com
Cc: jason@cygnus.com
Subject: Makefile.in patch
Date: Tue, 05 May 1998 16:32:00 -0000 [thread overview]
Message-ID: <199805051901.MAA13316@yorick.cygnus.com> (raw)
The current .SUFFIXES rule gets it backwards. .SUFFIXES is the set of
suffixes you *do* want to consider for implicit rules. Without this patch,
gmake -r ignores the .c.o rule.
Tue May 5 01:28:12 1998 Jason Merrill <jason@yorick.cygnus.com>
* Makefile.in: Fix .SUFFIXES.
Index: Makefile.in
===================================================================
RCS file: /egcs/carton/cvsfiles/egcs/gcc/Makefile.in,v
retrieving revision 1.90
diff -c -p -r1.90 Makefile.in
*** Makefile.in 1998/04/27 22:27:25 1.90
--- Makefile.in 1998/05/05 18:59:07
*************** RECOG_H = recog.h gansidecl.h
*** 701,708 ****
# End of language makefile fragments.
#\f
! # Avoid a lot of time thinking about remaking Makefile.in and *.def.
! .SUFFIXES: .in .def
Makefile: $(srcdir)/Makefile.in config.status $(srcdir)/version.c \
$(xmake_file) $(tmake_file) $(LANG_MAKEFILES)
--- 701,710 ----
# End of language makefile fragments.
#\f
! # The only suffixes we want for implicit rules are .c and .o, so clear
! # the list and add them. This speeds up GNU Make, and allows -r to work.
! .SUFFIXES:
! .SUFFIXES: .c .o
Makefile: $(srcdir)/Makefile.in config.status $(srcdir)/version.c \
$(xmake_file) $(tmake_file) $(LANG_MAKEFILES)
next reply other threads:[~1998-05-05 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-05 16:32 Jason Merrill [this message]
1998-05-06 11:49 ` Jim Wilson
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=199805051901.MAA13316@yorick.cygnus.com \
--to=jason@cygnus.com \
--cc=egcs@cygnus.com \
--cc=wilson@cygnus.com \
/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).