From mboxrd@z Thu Jan 1 00:00:00 1970 From: cgd@sibyte.com (Chris G. Demetriou) To: mdejong@cygnus.com (Mo DeJong) Cc: insight@sources.redhat.com Subject: Re: Lets rename insight to "insight" (imagine that) Date: Thu, 16 Nov 2000 15:32:00 -0000 Message-id: <5tg0krxzls.fsf@highland.sibyte.com> References: <5titpny3eu.fsf@highland.sibyte.com> X-SW-Source: 2000-q4/msg00235.html mdejong@cygnus.com (Mo DeJong) writes: > Some on disk numbers from my build: > > ls -la ~/project/install/insight/bin/gdb > -rwxr-xr-x 1 mo mo 8797610 Oct 26 09:36 /home/mo/project/install/insight/bin/gdb > > % ls -la /usr/bin/gdb > -rwxr-xr-x 1 root root 1290416 Mar 7 2000 /usr/bin/gdb I get something more like: 33 [highland] gas % ls -la /usr/local/sbtools-mips64-sb1sim-{1.3.10,1.4.9}/bin/mips64-sb1sim-gdb -rwxr-xr-x 1 root 6003252 Oct 1 18:37 /usr/local/sbtools-mips64-sb1sim-1.3.10/bin/mips64-sb1sim-gdb* -rwxr-xr-x 1 root 11415142 Oct 31 05:46 /usr/local/sbtools-mips64-sb1sim-1.4.9/bin/mips64-sb1sim-gdb* 34 [highland] gas % size /usr/local/sbtools-mips64-sb1sim-{1.3.10,1.4.9}/bin/mips64-sb1sim-gdb text data bss dec hex filename 2067527 47893 119652 2235072 221ac0 /usr/local/sbtools-mips64-sb1sim-1.3.10/bin/mips64-sb1sim-gdb 3906670 144000 209788 4260458 41026a /usr/local/sbtools-mips64-sb1sim-1.4.9/bin/mips64-sb1sim-gdb (solarisl host, "1.3.10" -> gdb 4.18 + mods, "1.4.9" -> gdb+insight from head of cvs as of a few weeks ago + mods. Both include 'sim' bits. I can't easily do a head-to-head comparison right now.) > Insight is a lot bigger than command line gdb. So, I think i'd disagree that it's _that_ much bigger. (2x, not 7x. but it'll change by platform, of course, and with availability of shlibs, etc.) > > I think, in general, that's probably the appropriate solution to the > > issue. > > That would still clobber the existing gdb. It means we can't > make an RPM for Insight because it would conflict with > the /usr/bin/gdb executable from regular gdb. Right, so, if what i proposed previously is deemed to be _not_ the right solution, then as far as I'm concerned, the code should: (1) build both gdb and insight binaries in the same source tree (differing in what code they link against). (2) install both. (3) provide configure options to disable build/install of one or the other. I'm not sure how spread out the checks for the window system are though -- it might be Hard to do this. as has been said by others, when you build insight, you really _do_ build a complete GDB, and that's what you get if you request the non-windowed version. It seems ... wasteful and, to me, wrong to require a completely separate build and install (incl. space for installed binaries) if you happen to want one version windowed and one version without. cgd