From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22872 invoked by alias); 12 Jan 2012 11:54:35 -0000 Received: (qmail 22864 invoked by uid 22791); 12 Jan 2012 11:54:34 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,TW_DB 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; Thu, 12 Jan 2012 11:54:21 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id EDAEA2BB22A; Thu, 12 Jan 2012 06:54:20 -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 B9xGL5R2gxbw; Thu, 12 Jan 2012 06:54:20 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 54CEE2BB16B; Thu, 12 Jan 2012 06:54:20 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id DF972145615; Thu, 12 Jan 2012 15:53:55 +0400 (RET) Date: Thu, 12 Jan 2012 12:35:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: asmwarrior@gmail.com, dje@google.com, gdb-patches@sourceware.org Subject: Re: Building GDB 7.3.92 with MinGW Message-ID: <20120112115355.GO31383@adacore.com> References: <83hb03e9sx.fsf@gnu.org> <838vlfe0k9.fsf@gnu.org> <4F0CD948.8080909@gmail.com> <4F0E266C.8080208@gmail.com> <20120112064721.GN31383@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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: 2012-01/txt/msg00401.txt.bz2 > > The only case when path "relocation" is turned off is when the user > > configured directories such as the gdb-datadir using a path that is > > not a subdir of the prefix. > > That latter case is what I had in mind. In general, it is a bad mojo > to force Windows users to install binaries in some specific tree or > under a certain parent directory. E.g., the binary could be > configured for d:/usr as a prefix, but installed in c:/foo/bar. This is not what I meant, or did I misunderstand you. Here is what I am trying to say. It is perfectly fine to do: % /path/to/gdb/configure --prefix=c:/usr/my-gdb % make % make install % cp -R c:/usr/my-gdb c:/foo/bar Relocations should still be working, and our own experience with that reveals no obvious problem. What I am saying is the following configure command will turn gdb-datadir relocation off: % /path/to/gdb/configure --prefix=c:/usr --with-gdbdatadir=c:/foo This is because c:/foo is not "inside" c:/usr. On other other hand, datadir relocation would still be active if --with-gdbdatadir was c:/usr/share/gdb-datadir. -- Joel