From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Subject: [commit, obvious] make check doesn't create gdb.python
Date: Thu, 16 Oct 2008 15:13:00 -0000 [thread overview]
Message-ID: <1224169956.6967.96.camel@localhost.localdomain> (raw)
Hi,
I just committed this fix from Paul Pluzhnikov, under the obvious rule.
His explanation:
> This is rather on the obious side: make check fails to create
> gdb.python (when build tree is separate from source tree).
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
2008-10-16 Paul Pluzhnikov <ppluzhnikov@google.com>
* Makefile.in: Add gdb.python to ALL_SUBDIRS.
Index: gdb/testsuite/Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/Makefile.in,v
retrieving revision 1.23
diff -u -r1.23 Makefile.in
--- gdb/testsuite/Makefile.in 28 Jul 2008 20:05:58 -0000 1.23
+++ gdb/testsuite/Makefile.in 16 Oct 2008 15:05:22 -0000
@@ -36,7 +36,7 @@
ALL_SUBDIRS = gdb.ada gdb.arch gdb.asm gdb.base gdb.cp gdb.disasm \
gdb.dwarf2 \
gdb.fortran gdb.server gdb.java gdb.mi \
- gdb.objc gdb.opt gdb.pascal gdb.threads gdb.trace \
+ gdb.objc gdb.opt gdb.pascal gdb.python gdb.threads gdb.trace \
gdb.xml \
$(SUBDIRS)
reply other threads:[~2008-10-16 15:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1224169956.6967.96.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=gdb-patches@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