From: "Rupert Wood" <me@rupey.net>
To: "'Steven Mueller'" <diffusor@ugcs.caltech.edu>
Cc: "'Dan Kegel'" <dank@kegel.com>, "'GCC Help list'" <gcc-help@gcc.gnu.org>
Subject: RE: sh4-cross-compiling-gcc-3.0.2 build fails during assembly
Date: Tue, 15 Jan 2002 02:13:00 -0000 [thread overview]
Message-ID: <616BE6A276E3714788D2AC35C40CD18D11FE3E@whale.softwire.co.uk> (raw)
In-Reply-To: <616BE6A276E3714788D2AC35C40CD18D2C5960@whale.softwire.co.uk>
Steven Mueller wrote:
> A quick search on Google indicates these types of errors are pretty
> common for a mismatching assembler architecture...
In your script:
| (
| ln -s sh4el-hardhat-linux sh4-linux
| cd bin
| ln -s sh_sh4_le-ar sh4-linux-ar
| ln -s sh_sh4_le-ld sh4-linux-ld
| ln -s sh_sh4_le-nm sh4-linux-nm
| ln -s sh_sh4_le-ranlib sh4-linux-ranlib
| ln -s sh_sh4_le-strip sh4-linux-strip
| )
you don't appear to set up sh4-linux-as. The new GCC, therefore, might
be using the host assembler.
You could try repeating the failing compile manually, adding '-v' to
check which assembler is being used.
Rup.
next parent reply other threads:[~2002-01-15 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <616BE6A276E3714788D2AC35C40CD18D2C5960@whale.softwire.co.uk>
2002-01-15 2:13 ` Rupert Wood [this message]
2002-01-14 17:09 Steven Mueller
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=616BE6A276E3714788D2AC35C40CD18D11FE3E@whale.softwire.co.uk \
--to=me@rupey.net \
--cc=dank@kegel.com \
--cc=diffusor@ugcs.caltech.edu \
--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).