From: Tom Tromey <tromey@redhat.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>, gdb-patches@sources.redhat.com
Subject: Re: RFA: automatic dependency tracking
Date: Fri, 08 Aug 2008 15:18:00 -0000 [thread overview]
Message-ID: <m363qbfse5.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1218206154.8002.6.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Fri\, 08 Aug 2008 11\:35\:54 -0300")
>>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:
Thiago> Only one issue though. Any reason why python.o and python-utils.o were
Thiago> left with the header dependencies?
Just an oversight.
Here is a patch. I tested it using GNU make (all I've got) but it
just applies the obvious transformation and should be safe in general.
I also moved the python bits up above the dependency-tracking bits,
for consistency.
Ok?
Tom
b/gdb/ChangeLog:
2008-08-08 Tom Tromey <tromey@redhat.com>
* Makefile.in (python.o): Remove dependencies. Use COMPILE and
POSTCOMPILE.
(python-utils.o): Likewise.
diff --git a/gdb/Makefile.in b/gdb/Makefile.in
index 0a61c24..7f8c9ea 100644
--- a/gdb/Makefile.in
+++ b/gdb/Makefile.in
@@ -1822,6 +1822,23 @@ tui-winsource.o: $(srcdir)/tui/tui-winsource.c
$(COMPILE) $(srcdir)/tui/tui-winsource.c
$(POSTCOMPILE)
+#
+# gdb/python/ dependencies
+#
+# Need to explicitly specify the compile rule as make will do nothing
+# or try to compile the object file into the sub-directory.
+
+# Flags needed to compile Python code
+PYTHON_CFLAGS=@PYTHON_CFLAGS@
+
+python.o: $(srcdir)/python/python.c
+ $(COMPILE) $(PYTHON_CFLAGS) $(srcdir)/python/python.c
+ $(POSTCOMPILE)
+
+python-utils.o: $(srcdir)/python/python-utils.c
+ $(COMPILE) $(PYTHON_CFLAGS) $(srcdir)/python/python-utils.c
+ $(POSTCOMPILE)
+
\f
#
@@ -1863,22 +1880,4 @@ $(all_object_files) : $(generated_files)
# Dependencies.
@GMAKE_TRUE@-include $(patsubst %.o, $(DEPDIR)/%.Po, $(all_object_files))
-#
-# gdb/python/ dependencies
-#
-# Need to explicitly specify the compile rule as make will do nothing
-# or try to compile the object file into the sub-directory.
-
-# Flags needed to compile Python code
-PYTHON_CFLAGS=@PYTHON_CFLAGS@
-
-python.o: $(srcdir)/python/python.c $(defs_h) $(python_h) \
- $(command_h) $(libiberty_h) $(cli_decode_h) $(charset_h) $(top_h) \
- $(exceptions_h) $(python_internal_h) $(version_h) $(cli_script_h) \
- $(ui_out_h) $(target_h) $(gdbthread_h)
- $(CC) -c $(INTERNAL_CFLAGS) $(PYTHON_CFLAGS) $(srcdir)/python/python.c
-python-utils.o: $(srcdir)/python/python-utils.c $(defs_h) $(python_internal_h)
- $(CC) -c $(INTERNAL_CFLAGS) $(PYTHON_CFLAGS) \
- $(srcdir)/python/python-utils.c -o python-utils.o
-
### end of the gdb Makefile.in.
next prev parent reply other threads:[~2008-08-08 15:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 22:14 Tom Tromey
2008-07-30 17:53 ` Pedro Alves
2008-07-30 19:12 ` Tom Tromey
2008-07-31 18:51 ` Pedro Alves
2008-07-31 10:48 ` Andrew STUBBS
2008-07-31 12:16 ` Tom Tromey
2008-07-31 14:43 ` Tom Tromey
2008-08-02 20:34 ` Thiago Jung Bauermann
2008-08-07 5:50 ` Ralf Wildenhues
2008-08-07 13:47 ` Tom Tromey
2008-08-07 13:53 ` Daniel Jacobowitz
2008-08-07 19:17 ` Ralf Wildenhues
2008-08-07 20:07 ` Tom Tromey
2008-08-07 20:46 ` Ralf Wildenhues
2008-08-07 20:51 ` Tom Tromey
2008-08-07 20:17 ` Daniel Jacobowitz
2008-08-07 20:22 ` Tom Tromey
2008-08-07 20:46 ` Ralf Wildenhues
2008-08-07 20:49 ` Tom Tromey
2008-08-07 20:59 ` Daniel Jacobowitz
2008-08-07 22:51 ` Ralf Wildenhues
2008-08-08 14:37 ` Thiago Jung Bauermann
2008-08-08 15:18 ` Tom Tromey [this message]
2008-08-08 15:24 ` Ralf Wildenhues
2008-08-08 17:27 ` Tom Tromey
2008-08-08 17:35 ` Daniel Jacobowitz
2008-08-07 17:09 ` Tom Tromey
2008-08-07 19:23 ` Ralf Wildenhues
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=m363qbfse5.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sources.redhat.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