From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30006 invoked by alias); 4 Dec 2012 14:40:19 -0000 Received: (qmail 29960 invoked by uid 22791); 4 Dec 2012 14:40:18 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_NO 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; Tue, 04 Dec 2012 14:40:13 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 96BBB2E34C; Tue, 4 Dec 2012 09:40:12 -0500 (EST) 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 1Buuw5SC2M5G; Tue, 4 Dec 2012 09:40:12 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 34D782E34B; Tue, 4 Dec 2012 09:40:12 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id C2B3AC373F; Tue, 4 Dec 2012 18:39:57 +0400 (RET) Date: Tue, 04 Dec 2012 14:40:00 -0000 From: Joel Brobecker To: Mark Kettenis Cc: gdb-patches@sourceware.org Subject: Re: [RFA/commit] Delete exc_request.defs. Message-ID: <20121204143957.GA31477@adacore.com> References: <1354628722-23336-1-git-send-email-brobecker@adacore.com> <201212041402.qB4E2YC3000453@glazunov.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201212041402.qB4E2YC3000453@glazunov.sibelius.xs4all.nl> User-Agent: Mutt/1.5.21 (2010-09-15) 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: 2012-12/txt/msg00061.txt.bz2 > I don't think this file can be deleted. At least not unless we want > to stop pretending GNU/Hurd is a viable OS. > > This file is referenced by config/i386/i386gnu.mh. Can you explain how this file is referenced? I only see references to .o files, but I don't see the relationship with the .defs file... Thanks! -- Joel