From: Kai Ruottu <kai.ruottu@wippies.com>
To: gcc-help@gcc.gnu.org
Subject: Re: aix cross(?)compiler
Date: Wed, 14 Dec 2011 11:16:00 -0000 [thread overview]
Message-ID: <4EE88569.7000704@wippies.com> (raw)
In-Reply-To: <CABJqhQPXhN0fHpJ=UDK6krzKMro9QWE7jU7Gf4xB+a+9rxMBfA@mail.gmail.com>
14.12.2011 10:36, JÄdrzej Dudkiewicz kirjoitti:
> Hi,
>
> I'm building gcc 4.6.2 (C and C++) on AIX 5.2 to compile for AIX
> 4.3.3. I copied libraries and /usr/ccs/bin (as, nm, ld and others)
> from 4.3.3 to sysroot/ directory on AIX 5.2.
>
> AS_FOR_TARGET=/home/jd/xcomp/sysroot/usr/ccs/bin/as \
> LD_FOR_TARGET=/home/jd/xcomp/sysroot/usr/ccs/bin/ld \
> STRIP_FOR_TARGET=/home/jd/xcomp/sysroot/usr/ccs/bin/strip \
> RANLIB_FOR_TARGET=/home/jd/xcomp/sysroot/usr/ccs/bin/ranlib \
> AR_FOR_TARGET=/home/jd/xcomp/sysroot/usr/ccs/bin/ar \
> NM_FOR_TARGET=/home/jd/xcomp/sysroot/usr/ccs/bin/nm \
This makes the build to differ from the normal cross GCC case
where GNU binutils are used as the target binutils. Here the
native AIX 4.3.3 binutils are used on a AIX 5.2 cross host
as the target binutils. So my stupid question is whether this
choice should work at all?
> --with-as=/home/jd/xcomp/sysroot/usr/ccs/bin/as \
> --with-ld=/home/jd//xcomp/sysroot/usr/ccs/bin/ld \
These AIX 4.3.3 'as' and 'ld' seemingly don't crash on AIX 5.2
but :
> /home/jd/xcomp/build/./gcc/xgcc -B/home/jd/xcomp/build/./gcc/
> -B/opt/xgcc/gcc-4.6.2/powerpc-ibm-aix4.3.3.0/bin/
> -B/opt/xgcc/gcc-4.6.2/powerpc-ibm-aix4.3.3.0/lib/ -isystem
> /opt/xgcc/gcc-4.6.2/powerpc-ibm-aix4.3.3.0/include -isystem
> /opt/xgcc/gcc-4.6.2/powerpc-ibm-aix4.3.3.0/sys-include
> --sysroot=/home/jd/xcomp/sysroot
what about the native AIX 4.3.3 'ld' understanding where the
target library stuff is? What the libgcc configure understood
about the target libraries?
If behaving normally, building GNU binutils for the AIX 5.2
$host and targeting to the AIX 4.3.3 $target and configuring
them using '--with-sysroot=' to search from $sysroot for the
AIX 4.3.3, there wouldn't be these suspicicions and stupid
questions... And any crash in the build would be a clear bug
but it is hard to say what this case really is.
next prev parent reply other threads:[~2011-12-14 11:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 8:36 Jędrzej Dudkiewicz
2011-12-14 9:45 ` Jonathan Wakely
2011-12-14 10:12 ` Jędrzej Dudkiewicz
2011-12-14 11:09 ` Jonathan Wakely
2011-12-14 11:29 ` Jędrzej Dudkiewicz
2011-12-14 12:07 ` Jonathan Wakely
2012-01-21 18:19 ` Paul Smith
2012-01-21 18:28 ` Marc Glisse
2012-01-21 18:37 ` Newer MPFR versions (was: Re: aix cross(?)compiler) Paul Smith
2012-01-21 18:51 ` aix cross(?)compiler Jonathan Wakely
2012-01-21 22:24 ` Paul Smith
2011-12-14 11:16 ` Kai Ruottu [this message]
2011-12-14 11:42 ` Jędrzej Dudkiewicz
2011-12-14 17:10 ` Kai Ruottu
2011-12-22 17:36 ` Jędrzej Dudkiewicz
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=4EE88569.7000704@wippies.com \
--to=kai.ruottu@wippies.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).