From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [rfa][testsuite] Consolidade Python test functions in lib/gdb.exp.
Date: Wed, 20 May 2009 15:10:00 -0000 [thread overview]
Message-ID: <1242832233.6644.2.camel@hactar> (raw)
In-Reply-To: <20090520145859.GA9276@caradoc.them.org>
Em Qua, 2009-05-20 Ã s 10:58 -0400, Daniel Jacobowitz escreveu:
> On Wed, May 20, 2009 at 10:18:07AM -0300, Thiago Jung Bauermann wrote:
> > Em Ter, 2009-05-19 Ã s 23:39 -0400, Daniel Jacobowitz escreveu:
> > > On Wed, May 20, 2009 at 12:26:17AM -0300, Thiago Jung Bauermann wrote:
> > > > >From my part, not at all! I would gladly remove the python- prefix from
> > > > everything.
> > >
> > > Note that all source files, unlike test cases, share a namespace: they
> > > all currently get dropped in gdb/*.o. So this may be tricky.
> >
> > If I do the renaming and successfully build GDB and run the python
> > testcases, does it show that there's no problem afoot?
>
> Probably, yes. I don't see how it could work though - python/frame.c
> -> frame.o would clobber gdb/frame.c -> frame.o.
Ah, I didn't think of python-frame.c. It didn't exist when I did this
back then. :-(
The right solution then is to make them not share a namespace.
Tromey, you're the makefile wizard: is there an easy and painless way to
make object files which come from different source directories in gdb/
to have different pathnames?
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2009-05-20 15:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 15:21 Thiago Jung Bauermann
2009-04-20 17:13 ` Tom Tromey
2009-04-20 17:23 ` Daniel Jacobowitz
2009-05-18 4:38 ` Thiago Jung Bauermann
2009-05-18 18:11 ` Eli Zaretskii
2009-05-19 14:50 ` Thiago Jung Bauermann
2009-05-19 14:59 ` Daniel Jacobowitz
2009-05-19 19:22 ` Eli Zaretskii
2009-05-19 22:21 ` Thiago Jung Bauermann
2009-05-20 3:11 ` Eli Zaretskii
2009-05-20 3:26 ` Thiago Jung Bauermann
2009-05-20 3:39 ` Daniel Jacobowitz
2009-05-20 13:18 ` Thiago Jung Bauermann
2009-05-20 14:59 ` Daniel Jacobowitz
2009-05-20 15:10 ` Thiago Jung Bauermann [this message]
2009-05-20 17:22 ` Eli Zaretskii
2009-05-20 19:39 ` Thiago Jung Bauermann
2009-05-20 20:00 ` Eli Zaretskii
2009-05-20 20:49 ` Thiago Jung Bauermann
2009-05-20 23:11 ` Joel Brobecker
2009-05-31 22:26 ` Thiago Jung Bauermann
2009-05-31 22:37 ` Thiago Jung Bauermann
2009-06-04 18:03 ` Tom Tromey
2009-05-28 0:43 ` Tom Tromey
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=1242832233.6644.2.camel@hactar \
--to=bauerman@br.ibm.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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