From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1577 invoked by alias); 19 Nov 2005 18:02:18 -0000 Received: (qmail 1569 invoked by uid 22791); 19 Nov 2005 18:02:17 -0000 X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 19 Nov 2005 18:02:17 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id jAJI2GS1023491 for ; Sat, 19 Nov 2005 13:02:16 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id jAJI2BV08378; Sat, 19 Nov 2005 13:02:11 -0500 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id jAJI29FM003367; Sat, 19 Nov 2005 13:02:10 -0500 Message-ID: <437F68A0.4020406@redhat.com> Date: Sat, 19 Nov 2005 18:04:00 -0000 From: Keith Seitz User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929) MIME-Version: 1.0 To: Michael Stather CC: insight@sources.redhat.com Subject: Re: AW: AW: Building insight independantly of gdb References: <20051119174003.E743351819B@h8391.serverkompetenz.net> In-Reply-To: <20051119174003.E743351819B@h8391.serverkompetenz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2005-q4/txt/msg00029.txt.bz2 Michael Stather wrote: > Well I did *g Sorry, I just hit "reply" > So is it possible to install insight but not the included gdb?I mean with > configure switches? There is no way to do this with configure flags. That leaves you two options: 1) Copy /usr/local/bin/gdb; install insight; clobber newly-installed gdb with copy 2) Specify --prefix=$INSTALLDIR to configure, build, install, remove $INSTALLDIR/bin/gdb, then copy the contents to /usr/local. (Or simply use the new installdir and add that path to the end of your current PATH.) Keith > -----Ursprüngliche Nachricht----- > Von: Keith Seitz [mailto:keiths@redhat.com] > Gesendet: Samstag, 19. November 2005 17:58 > An: Michael Stather > Betreff: Re: AW: Building insight independantly of gdb > > Please post to the mailing list for the benefit of others. > > Keith > > Michael Stather wrote: > >>Thanks for the explanation. >>I´ve a SuSE system where gdb is installed as a rpm package. And I >>use/test several IDEs which use GDB as a debugger. >>So I don´t want insight to interfere with my gdb installation. I like >>to use it as a "seperate" program which uses it´s included gdb while >>other apps which request gdb use the installed one. >>The thing with the path doesn´t work since /usr/local/bin appears >>before /usr/bin (where my installed gdb is) Can I configure switches >>(or whatever) to have insight compiled without installing gdb (but >>still using it). This would IMHO be the only possibility to install >>insight without interferring an installed gdb? >> >>-----Ursprüngliche Nachricht----- >>Von: Keith Seitz [mailto:keiths@redhat.com] >>Gesendet: Samstag, 19. November 2005 17:22 >>An: Michael Stather >>Cc: insight@sources.redhat.com >>Betreff: Re: Building insight independantly of gdb >> >>Michael Stather wrote: >> >> >>>As I read from the "about" page insight is a GUI for gdb. But it seems >>>to be built as a "gdb" executable mixing native gdb functionality with >>>a >> >>gui. >> >>Unlike ddd, eclipse, and many other guis for gdb, Insight *is* gdb. >>They are the same executable. This means that insight is orders of >>magnitude faster than the rest. >> >> >> >>>But if insight replaces my existing gdb other gdb GUIs and apps which >>>use gdb don´t work anymore. >>>Can I compile insight independant from gdb, so that it doesn´t >>>interfere with an existing gdb installation. The actual executable >>>should be named "insight" then. >> >> >>When you build gdb/insight, you get two executables: "gdb" and "insight". >>Both are identical except that one defaults to starting up the GUI >>(insight) and one does not. >> >>Other than file size, the presence of the insight code in the gdb >>executable does not alter the gdb executable: you basically still have a >> gdb release, compatible (if not identical) with any release of gdb >>with the same version. >> >>If you require to keep some other version of gdb, simply don't install >>the one that is built with insight. Only install the insight executable. >>[In practice, its probably easiest to install both executables into, >>e.g., /usr/local, and put your other gdb into. e.g., /usr/bin. Setting >>your PATH will then grab the right one at the right time.] >> >>Although I admit, I find this a bit weird. Are you saying that you >>want to use different versions of gdb, one when running the command >>line (or some other spawn-gdb GUI) and one when running insight? >>