From: Michael Haubenwallner <michael.haubenwallner@salomon.at>
To: Bill McEnaney <bill@rkirkpat.net>
Cc: Benjamin Modra <ben.modra@yahoo.com.au>, gcc-help@gcc.gnu.org
Subject: Re: Slow build
Date: Thu, 16 Jul 2009 09:26:00 -0000 [thread overview]
Message-ID: <1247734995.1554.105.camel@salomon-22> (raw)
In-Reply-To: <20090715205647.A882271813@saratoga.rkirkpat.net>
On Wed, 2009-07-15 at 14:56 -0600, Bill McEnaney wrote:
> My Sunblade 100 takes almost 20 hours to build gcc with the machine's
> 500 MHz UltrSPARC-II processor and its 64-bit bus. So to build that
> software, I usually launch a batch process with the "batch" command.
Sometimes it also depends on the shell being used. On some AIX for
example (c,c++ only), using /bin/sh (the default) it takes >24 hours,
compared to ~1.5 hours when using bash (CONFIG_SHELL=/path/to/bash).
/haubi/
>
> Bill
> >
> > Three full days to build gcc and its still running.. Does this seem
> excessive??
> > Cygwin on XP @ 3GHz, nothing else running, web disconnected, idle
> processor. Are all unix installs like this?
> > -Ben
> >
> >
> >
> >
> ____________________________________________________________________________________
> > Access Yahoo!7 Mail on your mobile. Anytime. Anywhere.
> > Show me how: http://au.mobile.yahoo.com/mail
> >
> >
>
> ________________________________________________________________
> Please visit a saintly hero:
> http://www.jakemoore.org
next prev parent reply other threads:[~2009-07-16 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 20:56 Bill McEnaney
2009-07-15 21:08 ` Tim Prince
2009-07-16 9:26 ` Michael Haubenwallner [this message]
2009-07-16 12:05 ` Dr. David Kirkby
2009-07-16 12:54 ` Kai Ruottu
2009-07-16 12:59 ` Kai Ruottu
2009-07-18 0:07 ` Dr. David Kirkby
-- strict thread matches above, loose matches on Subject: below --
2009-07-21 2:05 Slow Build Benjamin Modra
2009-07-15 20:56 Slow build Dennis Clarke
2009-07-15 20:49 Benjamin Modra
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=1247734995.1554.105.camel@salomon-22 \
--to=michael.haubenwallner@salomon.at \
--cc=ben.modra@yahoo.com.au \
--cc=bill@rkirkpat.net \
--cc=gcc-help@gcc.gnu.org \
/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).