From: David Edelsohn <dje@watson.ibm.com>
To: James.Parker@saaconsultants.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: installing GCC 3.4.4 on cygwin targeting AIX-4.3.3
Date: Mon, 19 Sep 2005 16:21:00 -0000 [thread overview]
Message-ID: <200509191621.j8JGLaq31184@makai.watson.ibm.com> (raw)
In-Reply-To: <OFF8444372.2094481D-ON80257081.0031C218-80257081.00395C7C@SAAConsultants.com>
We do not seem to be communicating well. I suggest that you
invoke the compile command manually with the -v verbose flag and see where
the cross-compiler is finding the assembler. Not compiler and assembler
print version options. In other words, go to the build directory and
manually invoke
/usr/src/BUILD/gcc/gcc/xgcc -B/usr/src/BUILD/gcc/gcc/ -B/usr/local/cross-tools/rs6000-ibm-aix4.3.3.0/bin/ ... -mcpu=power -DL_divdi3 -c /usr/src/gcc-3.4.4/gcc/libgcc2.c -fexceptions -fnon-call-exceptions -v
The entire command It will print the sub-programs that it is invoking and
the options that it is using. Then you can determine if it is invoking
the wrong assembler or manually invoke the assembler on an assembly file
containing "mfcr" to investigate further.
David
prev parent reply other threads:[~2005-09-19 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 14:21 James.Parker
2005-09-16 19:20 ` David Edelsohn
2005-09-19 10:24 ` James.Parker
2005-09-19 16:21 ` David Edelsohn [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=200509191621.j8JGLaq31184@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=James.Parker@saaconsultants.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).