public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: fedor_qd@mail.ru
To: "Paul Lucas" <plucas@splunk.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Building Linux x86_64 to AIX PowerPC cross-compiler
Date: Tue, 14 Jun 2022 21:33:31 +0300	[thread overview]
Message-ID: <1655231611.35054132@f13.my.com> (raw)
In-Reply-To: <8109E6B6-F99A-473B-9E8B-A540FC7679CD@splunk.com>


Do you build cross binutils before gcc? Check them carefully.
Before build in shell use "export LDFLAGS+= -v " for verbose output.
--
Sent from Outlook Email App for Android аўторак, 14 чэрвеня 2022, 07:28PM +03:00 from Paul Lucas via Gcc-help  gcc-help@gcc.gnu.org :

>Hi there -
>
>I want to build a cross-compiler from Linux x86_64 (host) to AIX PowerPC (target).  Eventually, while building gcc, I get:
>
> collect2: fatal error: libgcc.a: cannot open as COFF file
>
>While Linux uses ELF and AIX uses coff, I would have assumed that the binutils I built for the cross-compiler would have produced a linker that was able to link COFF files.
>
>The configure for binutils was:
>
> configure --disable-gold --prefix=/aix-powerpc --disable-multilib --disable-nls --target=powerpc-ibm-aix7.1.0.0 --with-sysroot=/aix-powerpc --with-arch=powerpc --disable-werror --enable-plugins
>
>where /aix-powerpc contains headers and libraries copied from a live AIX system.
>
>Apparently back in 2016 on this same mailing list:
>
>https://gcc.gnu.org/legacy-ml/gcc-help/2016-10/msg00108.html
>
>somebody was trying to build the same cross-compiler and got the same error.  Unfortunately, there’s no answer there. The only advice given was:
>
> Judicious use of "-v" can help spot calling the wrong linker, linking the wrong libraries, wrong header file include paths, etc.
>
>
>Can anyone perhaps give a _little_ more help?
>
>Thanks.
>
>- Paul
>

  reply	other threads:[~2022-06-14 18:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 16:18 Paul Lucas
2022-06-14 18:33 ` fedor_qd [this message]
2022-06-15 11:36 ` Kai Ruottu
2022-06-15 23:06   ` Brian Groose

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=1655231611.35054132@f13.my.com \
    --to=fedor_qd@mail.ru \
    --cc=gcc-help@gcc.gnu.org \
    --cc=plucas@splunk.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).