From: Brian Groose <brian@groose.com>
To: Kai Ruottu <kai.ruottu@wippies.com>
Cc: Paul Lucas <plucas@splunk.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Building Linux x86_64 to AIX PowerPC cross-compiler
Date: Wed, 15 Jun 2022 19:06:12 -0400 [thread overview]
Message-ID: <CAKMEP22cyOpQQPt98LK+CsKTQRe8CqmMFGUekkaTq-gRPf5wOw@mail.gmail.com> (raw)
In-Reply-To: <e6f2c471-9599-7d48-46c3-33d30e13e4d0@wippies.com>
On Wed, Jun 15, 2022 at 7:37 AM Kai Ruottu <kai.ruottu@wippies.com> wrote:
>
> Paul Lucas via Gcc-help kirjoitti 14.6.2022 klo 19.18:
> > 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.
>
>
> The GNU Install documents for target platforms :
>
> https://gcc.gnu.org/install/specific.html#x-ibm-aix
>
> are saying :
>
> "The native |as| and |ld| are recommended for bootstrapping on AIX. The
> GNU Assembler, GNU Linker, and GNU Binutils version 2.20 is the minimum
> level that supports bootstrap on AIX 5. The GNU Assembler has not been
> updated to support AIX 6 or AIX 7. The native AIX tools do interoperate
> with GCC."
>
> So it seems that AIX 6 and AIX 7 aren't supported in GNU binutils :(
>
> The biggest problem in this issue probaly is that so few people can get
> the "headers and libraries copied from a live AIX system". Or IBM or
> something would provide them freely
> for everyone wanting to make crosscompilers for AIX. Those who have AIX
> systems just produce native GNU tools and are happy. Others aren't
> interested to work with cross
> tools they cannot make...
> For instance the Sun Solaris2 headers and libraries have beem freely
> available just like the whole Sparc/x86 operating systems. So anyone
> could have procuded crosstools for these
> platforms if having the required know-how for building GNU tools.
I had also tried to get a Linux x86_64 cross compiler targeting AIX 6.1 several
years ago and was never able to make it work, the issue was always binutils
and not gcc. Even when I compiled native binutils and gcc on AIX 6.1 I ended
up using the AIX versions of as/ld/ar/etc since they worked more reliably than
the binutils versions. I eventually gave up on a cross compiler and continued
to natively compile, though cross compilation would have been a much nicer and
more scalable system.
I recall bumping into the docs that Kai quoted here, which confirmed
that it just
wasn't going to work since there was effectively no assembler that worked.
prev parent reply other threads:[~2022-06-15 23:06 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
2022-06-15 11:36 ` Kai Ruottu
2022-06-15 23:06 ` Brian Groose [this message]
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=CAKMEP22cyOpQQPt98LK+CsKTQRe8CqmMFGUekkaTq-gRPf5wOw@mail.gmail.com \
--to=brian@groose.com \
--cc=gcc-help@gcc.gnu.org \
--cc=kai.ruottu@wippies.com \
--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).