public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom Kacvinsky <tkacvins@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Building gcc 4.9.2 on AIX 7.1
Date: Sun, 11 Jun 2023 12:27:18 -0400	[thread overview]
Message-ID: <CAG_eJLd3aZXgqat8Df5Jw4W2ZsKwkk6ZGjta9tF4GExvPGf8Mg@mail.gmail.com> (raw)
In-Reply-To: <86815941-E3AC-494F-A1E8-89544D4234A6@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]

HI,

For some reason my follow-up hasn't made it through.

On Sun, Jun 11, 2023 at 11:27 AM Tom Kacvinsky <tkacvins@gmail.com> wrote:

<snip>


> Those aren't binutils linker warnings.  Those are coming from the system
> linker.  Which probably means you are using the system assembler, too.  Or
> maybe even the odd case where you're using binutils for the assembler but
> the system linker.
>
> Can you try with using binutils for the assembler and linker?  I am
> assuming you either have an older version of GCC for building the newer
> version of it, or perhaps you have the Sun Pro compilers.  In any case, you
> could use whichever bootstrap compiler you have to build binutils, and then
> put they binutils in PATH.  The GCC configure script should then chose
> those for building.


I missed that you're on AIX.  So either you're using an older version of
GCC to bootstrap, or IBM's xlc/xlC compilers to bootstrap.

Here is a thought I had up re-thinking this.  This might be an
architecture problem.  Which version of the POWER chips are you using?
YOu might have to force the GCC configuration process to use -march to
specify the right processor.  But as far as I know, the configure script
should be smart enough to figure that out.

It's been about ten years since I used the xlc/xlC compilers, so I am
not sure how one would select the architecture they want.

  reply	other threads:[~2023-06-11 16:27 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 [this message]
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
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=CAG_eJLd3aZXgqat8Df5Jw4W2ZsKwkk6ZGjta9tF4GExvPGf8Mg@mail.gmail.com \
    --to=tkacvins@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).