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 [thread overview]
Message-ID: <5tg0krxzls.fsf@highland.sibyte.com> (raw)
In-Reply-To: <mailpost.974414965.29758@postal.sibyte.com>
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
next prev parent reply other threads:[~2000-11-16 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 13:38 Mo DeJong
[not found] ` <mailpost.974410715.28880@postal.sibyte.com>
2000-11-16 14:10 ` Chris G. Demetriou
2000-11-16 14:22 ` Duane Ellis
2000-11-16 14:45 ` Mo DeJong
[not found] ` <mailpost.974414965.29758@postal.sibyte.com>
2000-11-16 15:32 ` Chris G. Demetriou [this message]
2000-11-19 3:24 ` Eray Ozkural (exa)
2000-11-16 15:57 ` Eray Ozkural (exa)
[not found] <974414704.20985.ezmlm@sources.redhat.com>
2000-11-16 15:20 ` Jim Ingham
2000-11-16 15:39 ` Mo DeJong
[not found] ` <mailpost.974418021.30668@postal.sibyte.com>
2000-11-16 18:01 ` Chris G. Demetriou
2000-11-16 16:34 Fabrice Gautier
2000-11-19 3:19 ` Eray Ozkural (exa)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5tg0krxzls.fsf@highland.sibyte.com \
--to=cgd@sibyte.com \
--cc=insight@sources.redhat.com \
--cc=mdejong@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).