From: Stan Shebs <shebs@apple.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: Stephen Smith <ischis2@home.com>, GDB <gdb@sourceware.cygnus.com>
Subject: Re: Snapshot of 3/6/2001
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <3AA8162A.2E0FC164@apple.com> (raw)
In-Reply-To: <1010308213929.ZM1528@ocotillo.lan>
Kevin Buettner wrote:
>
> On Mar 8, 2:24pm, Stephen Smith wrote:
>
> > It tool 2.5 hours for insight gdb to configure and compile up to the utils/spu directory. How long should
> > it take for that section to compile - I am up to 1.5 hours.
>
> That seems excessive. I just tried it on one of my machines and it
> finished in a matter of seconds.
I bet he's doing a "./configure; make" so it's all happening
at once.
> The other thing I noticed is that this is not built by default, so
> I'm wondering how you ended up building utils/spu in the first place?
utils/spu is the last directory in the GDB package, so if the machine is
hanging at the end of the configure or doing something silent after
running configure, it will look like it's hanging there.
Stan
prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 15:59 Stephen Smith
2001-03-21 15:59 ` Kevin Buettner
2001-03-21 15:59 ` Stan Shebs [this message]
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=3AA8162A.2E0FC164@apple.com \
--to=shebs@apple.com \
--cc=gdb@sourceware.cygnus.com \
--cc=ischis2@home.com \
--cc=kevinb@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