From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28372 invoked by alias); 13 Jan 2012 10:55:19 -0000 Received: (qmail 28363 invoked by uid 22791); 13 Jan 2012 10:55:18 -0000 X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 13 Jan 2012 10:55:04 +0000 Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LXQ00K00GYTR000@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Fri, 13 Jan 2012 12:54:38 +0200 (IST) Received: from HOME-C4E4A596F7 ([77.124.136.230]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LXQ00JWBGZ1V0C0@a-mtaout20.012.net.il>; Fri, 13 Jan 2012 12:54:37 +0200 (IST) Date: Fri, 13 Jan 2012 11:06:00 -0000 From: Eli Zaretskii Subject: Re: Building GDB 7.3.92 with MinGW In-reply-to: <20120111032441.GE31383@adacore.com> To: Joel Brobecker Cc: gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <83ty3zkh3g.fsf@gnu.org> References: <83hb03e9sx.fsf@gnu.org> <20120111032441.GE31383@adacore.com> X-IsSubscribed: yes 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/msg00465.txt.bz2 > Date: Wed, 11 Jan 2012 07:24:41 +0400 > From: Joel Brobecker > Cc: gdb-patches@sourceware.org > > > 2. "make install-strip" fails in readline/, in sim/, and in gdb/: > [...] > > Finally, a question: Why are we installing libraries (libbfd, > > libopcodes, libiberty) and the standards.info manual? The libraries > > are not part of GDB, we import them from elsewhere. "make install" > > will happily overwrite existing installation of these libraries that > > could potentially be newer, coming from their respective upstream > > distributions. How about removing these from "make install"? > > We could side-step these issues by documenting in the README that > GDB should be installed using "make -C gdb install", or "make -C > gdb install-strip". This is what I personally do. I like this alternative the best. Is the patch below OK to install, including on the branch? Index: gdb/README =================================================================== RCS file: /cvs/src/src/gdb/README,v retrieving revision 1.49 diff -u -r1.49 README --- gdb/README 4 Jan 2012 04:11:38 -0000 1.49 +++ gdb/README 13 Jan 2012 10:52:12 -0000 @@ -39,6 +39,11 @@ cd gdb-VERSION ./configure make + cd gdb + make install (or "make install-strip") + +Alternatively, install with + cp gdb/gdb /usr/local/bin/gdb (or wherever you want) However, we recommend that an empty directory be used instead. @@ -52,7 +57,8 @@ cd build /gdb-VERSION/configure make - cp gdb/gdb /usr/local/bin/gdb (or wherever you want) + cd gdb + make install (or "make install-strip") (Building GDB with DJGPP tools for MS-DOS/MS-Windows is slightly different; see the file gdb-VERSION/gdb/config/djgpp/README for details.) @@ -236,6 +242,15 @@ configuration files for every directory level underneath (unless you tell it not to, with the `--norecursion' option). + After the build finishes successfully, you can install the built +GDB like this: + + cd gdb + make install + + If you want to install a GDB binary stripped of debugging symbols, +type "make install-strip" instead of the second line. + You can install `gdb' anywhere; it has no hardwired paths. However, you should make sure that the shell on your path (named by the `SHELL' environment variable) is publicly readable. Remember that GDB uses the