From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13579 invoked by alias); 23 Feb 2011 03:51:22 -0000 Received: (qmail 13570 invoked by uid 22791); 23 Feb 2011 03:51:21 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.codesourcery.com (HELO mail.codesourcery.com) (38.113.113.100) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 23 Feb 2011 03:51:16 +0000 Received: (qmail 30598 invoked from network); 23 Feb 2011 03:51:14 -0000 Received: from unknown (HELO ?0.0.0.0?) (yao@127.0.0.2) by mail.codesourcery.com with ESMTPA; 23 Feb 2011 03:51:14 -0000 Message-ID: <4D64842F.4010903@codesourcery.com> Date: Wed, 23 Feb 2011 03:51:00 -0000 From: Yao Qi User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Joel Brobecker CC: Michael Snyder , "gdb@sourceware.org" Subject: Re: make clean doesn't run in gdbserver/common References: <4D642638.8090207@vmware.com> <4D647F61.5080307@codesourcery.com> <20110223033606.GO2617@adacore.com> In-Reply-To: <20110223033606.GO2617@adacore.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-02/txt/msg00128.txt.bz2 On 02/23/2011 11:36 AM, Joel Brobecker wrote: > 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. 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. 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. -- Yao (齐尧)