public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jan-Frode Myklebust <janfrode@parallab.uib.no>
To: dje@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/5644: Building g++ on AIX 5.1 seems to loop forever.
Date: Sun, 28 Apr 2002 14:36:00 -0000	[thread overview]
Message-ID: <20020428213600.5905.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/5644; it has been noted by GNATS.

From: Jan-Frode Myklebust <janfrode@parallab.uib.no>
To: dje@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: bootstrap/5644: Building g++ on AIX 5.1 seems to loop forever.
Date: Sun, 28 Apr 2002 23:30:05 +0200

 On Fri, Apr 26, 2002 at 07:39:10PM -0000, dje@gcc.gnu.org wrote:
 
 >     Other people are successfully bootstrapping GCC 3.0.4 on AIX.  I think you are confusing building the various multilibs with looping forever.
 
 Yes, you're correct. This was pointed out by Roger Sayle
 <roger@eyesopen.com> about a month ago (don't know why the gnats page
 doesn't show this..). There were also a couple of suggestions for how
 to speed this up on AIX, f.ex.
 http://gcc.gnu.org/ml/gcc/2002-03/msg00086.html and defining
 CONFIG_SHELL=/usr/local/bin/bash.
 
 It actually took 10 hours to build gcc-3.0.4 on a single POWER4 cpu.
 
 
    -jf


             reply	other threads:[~2002-04-28 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-28 14:36 Jan-Frode Myklebust [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-26 12:39 dje
2002-03-13 14:56 Jan-Frode Myklebust
2002-03-13 13:39 dje
2002-02-09 12:26 janfrode

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=20020428213600.5905.qmail@sources.redhat.com \
    --to=janfrode@parallab.uib.no \
    --cc=dje@gcc.gnu.org \
    --cc=gcc-prs@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).