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 03:36:00 -0000 [thread overview]
Message-ID: <20110223033606.GO2617@adacore.com> (raw)
In-Reply-To: <4D647F61.5080307@codesourcery.com>
> gdb/gdbserver/
>
> * Makefile.in (CLEANDIRS, REQUIRED_SUBDIRS): New variable.
> (subdir_do): New make target. Copied from gdb/Makefile.
> (maintainer-clean, realclean, distclean, clean): Call corresponding
> make targets in common/Makefile.
What happens if you do a "make distclean" on a platform where both GDB
& GDBserver get built automatically in one "make"? It looks like we
will first do a distclean in gdb/ first, deleting gdb/common/Makefile,
and then do a distclean in gdbserver/, which will try to do a distclean
a second time in gdb/common, no? The second one will fail due to the
missing Makefile.
--
Joel
next prev parent reply other threads:[~2011-02-23 3:36 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 [this message]
2011-02-23 3:51 ` Yao Qi
2011-02-23 4:29 ` Joel Brobecker
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=20110223033606.GO2617@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