From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15433 invoked by alias); 27 Apr 2011 16:18:25 -0000 Received: (qmail 15370 invoked by uid 22791); 27 Apr 2011 16:18:20 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 27 Apr 2011 16:18:05 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 471BB2BAB5D; Wed, 27 Apr 2011 12:18:05 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9sxc0Cz6H3ce; Wed, 27 Apr 2011 12:18:05 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 1CAC92BAAFA; Wed, 27 Apr 2011 12:18:05 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id E2CF5145615; Wed, 27 Apr 2011 09:18:02 -0700 (PDT) Date: Wed, 27 Apr 2011 16:18:00 -0000 From: Joel Brobecker To: Yao Qi Cc: gdb-patches@sourceware.org Subject: Re: New ARI warning Wed Apr 27 01:54:55 UTC 2011 Message-ID: <20110427161802.GC2489@adacore.com> References: <20110427015455.GA24839@sourceware.org> <4DB78A74.9060105@codesourcery.com> <20110427150815.GB2489@adacore.com> <4DB83ACB.6080503@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DB83ACB.6080503@codesourcery.com> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-04/txt/msg00513.txt.bz2 > Yes, I agree. So far, gdb code is using gdb_wait.h and gdbserver is > using sys/wait.h. gdb_wait.h looks quite independent of gdb or > gdbserver. Is there any known reason that we can't use gdb_wait.h in > gdbserver? I don't see any. You need to make sure that both configures test for sys/wait.h and wait.h. I looked at gdbserver's configure, and it is missing the check for wait. -- Joel