From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <yao@codesourcery.com>
Cc: Michael Snyder <msnyder@vmware.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: make clean doesn't run in gdbserver/common
Date: Wed, 23 Feb 2011 04:29:00 -0000 [thread overview]
Message-ID: <20110223042918.GP2617@adacore.com> (raw)
In-Reply-To: <4D64842F.4010903@codesourcery.com>
> There are two common dirs in build tree, under gdb/ and gdbserver/
> respectively, so it is not a problem to run 'make distclean' on top of
> gdb build tree.
Aha, OK. Thanks for the explanation.
> When building native gdb, it is redundant here to build libcommon.a for
> the same target twice, but given gdb and gdbserver should be built
> separately, we have to build libcommon.a separately. Yes, we can think
> of a method to build libcommon.a once when building a native gdb.
Given that this isn't going to work in the cross case (where gdbserver
is going to be cross-compiled), I am not sure that it's really worth
the effort and/or complication (if any).
--
Joel
prev parent reply other threads:[~2011-02-23 4:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 21:10 Michael Snyder
2011-02-23 3:31 ` Yao Qi
2011-02-23 3:36 ` Joel Brobecker
2011-02-23 3:51 ` Yao Qi
2011-02-23 4:29 ` Joel Brobecker [this message]
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=20110223042918.GP2617@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=msnyder@vmware.com \
--cc=yao@codesourcery.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