From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21431 invoked by alias); 8 Oct 2012 20:13:45 -0000 Received: (qmail 21418 invoked by uid 22791); 8 Oct 2012 20:13:44 -0000 X-SWARE-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from server-nat-6.cs.umd.edu (HELO bacon.cs.umd.edu) (128.8.127.149) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 08 Oct 2012 20:13:36 +0000 Received: from [10.109.175.173] (129-2-129-155.wireless.umd.edu [129.2.129.155]) (Authenticated sender: khooyp) by bacon.cs.umd.edu (Postfix) with ESMTPSA id D40CBB40A21; Mon, 8 Oct 2012 16:13:33 -0400 (EDT) Subject: Re: [PATCH] Also install data-directory into the build directory as computed by relocate_gdb_directory Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Khoo Yit Phang In-Reply-To: Date: Mon, 08 Oct 2012 20:13:00 -0000 Cc: Khoo Yit Phang , Joel Brobecker , Jan Kratochvil , GDB Patches Content-Transfer-Encoding: quoted-printable Message-Id: References: <9F52A338-A158-44DC-90C1-F46503859613@cs.umd.edu> <285502C6-1395-4049-9D55-031EDA3AD06D@cs.umd.edu> <20120924170348.GI4146@adacore.com> <20120927091737.GB2980@adacore.com> <20121004000840.GI3028@adacore.com> <20121004013358.GJ3028@adacore.com> <20121004145105.GP3028@adacore.com> <970CCEFD-FF30-4ED4-9ED9-F9C6A5400120@cs.umd.edu> To: Doug Evans X-CSD-MailScanner-ID: D40CBB40A21.A12CC X-CSD-MailScanner: Found to be clean X-CSD-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-50, required 5, autolearn=not spam, ALL_TRUSTED -50.00) X-CSD-MailScanner-From: khooyp@cs.umd.edu X-CSD-MailScanner-Watermark: 1350332015.02953@1YC/mY6NNpUIvIaM4+itvw 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-10/txt/msg00137.txt.bz2 Hi, On Oct 8, 2012, at 12:33 PM, Doug Evans wrote: > On Sat, Oct 6, 2012 at 12:02 PM, Khoo Yit Phang wrote: >> I prefer just installing data-directory into $BUILDDIR/share/data-direct= ory, which is simple and works as long as gdb isn't configured with --bindi= r, --exec-prefix, and/or --with-gdb-datadir that are too unusual. It should= cover most purposes of running gdb from the build directory, since I don't= see much reason to change --bindir, --exec-prefix, and/or --with-gdb-datad= ir if gdb won't be installed, unless for testing those flags, in which case= gdb will likely have to be installed anyways. Does anyone currently have a= use case I'm missing? >=20 > I'm not entirely comfortable with having normal makes (as in "make > all") create files outside of its build directory (and by this I mean > $obj/gdb/../anything). [And obviously I'm not including "make > install" here. :-)] > I'd prefer passing -bd (for build directory), for example. > [Not the best name choice since -b specifies the serial port baud > rate. -bt for build tree, and -B are alternatives.] >=20 > I could also go with a configure option to create a second gdb binary > for use in the build tree. > I would never use it, but as long as those that want it agree to > maintain it, 'tis ok with me. > Neither the testsuite, nor anything else, can depend on it - it would > just be for developer convenience sake. What about a configure option to enable "make all" to install to $obj/gdb/.= ./share/gdb? With ample warnings about caveats, and for developer convenien= ce only, of course. Yit October 8, 2012