public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christer Solskogen <christer.solskogen@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Building gcc 4.9.2 on AIX 7.1
Date: Tue, 13 Jun 2023 09:38:09 +0200	[thread overview]
Message-ID: <u696d2$khf$1@ciao.gmane.io> (raw)
In-Reply-To: <CA+DxmauCqmDEakusTt-nLOVhmjccjdyNXXE1+2X=4BxQpcZaqw@mail.gmail.com>

On 12.06.2023 17:54, Randy Galbraith via Gcc-help wrote:

> Hi Jonathan. Even though using GCC 13 may not work for us, I decided to
> test the build of gcc-13.1.0 (with gmp-6.2.1, mpfr-4.2.0 and mpc-1.3.1):
> 
> ./configure --enable-languages=c,c++
> make
> 
> Alas it seems to run into the same issue wherein ./conftest runs forever
> (>1hr, 40min, with 32:22 of cpu time). I'm now going to try export CC=xlc
> and see if I can get gcc 5.4.0 to build. Cheers, -Randy
> 

Don't build gcc from the source directory. This is not supported.
https://gcc.gnu.org/wiki/InstallingGCC

-- 
chs


  reply	other threads:[~2023-06-13  7:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11 12:26 Randy Galbraith
2023-06-11 15:27 ` Tom Kacvinsky
2023-06-11 16:27   ` Tom Kacvinsky
2023-06-11 19:04     ` Randy Galbraith
2023-06-11 21:04       ` Jonathan Wakely
2023-06-11 22:37         ` Randy Galbraith
2023-06-12 15:54           ` Randy Galbraith
2023-06-13  7:38             ` Christer Solskogen [this message]
2023-06-13 10:35               ` Randy Galbraith
2023-06-15 16:44                 ` Randy Galbraith
2023-06-15 22:05                   ` Jonathan Wakely
2023-06-16 19:46                     ` Randy Galbraith
2023-06-11 18:31 ` Kai Ruottu
2023-06-11 22:23   ` Randy Galbraith
2023-06-12 22:50 David Edelsohn
2023-06-13 10:29 ` Randy Galbraith
2023-06-13 10:42   ` Jonathan Wakely

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='u696d2$khf$1@ciao.gmane.io' \
    --to=christer.solskogen@gmail.com \
    --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).