public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Kazu Hirata <kazu@cs.umass.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: target/8441: GCC 3.2 fails in building of H8300 target
Date: Thu, 07 Nov 2002 06:06:00 -0000 [thread overview]
Message-ID: <20021107140605.9944.qmail@sources.redhat.com> (raw)
The following reply was made to PR target/8441; it has been noted by GNATS.
From: Kazu Hirata <kazu@cs.umass.edu>
To: evanlanglois@yahoo.com
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: target/8441: GCC 3.2 fails in building of H8300 target
Date: Thu, 07 Nov 2002 09:02:35 -0500 (EST)
Hi Evan,
> When building a cross compiler, the make barfs with some odd errors
> in the assembler. I didn't use any special options other than
> specifying the target as h8300-elf. I'm attempting to build a cross
> compiler for building Linux kernel for the h8300 series.
Do you have binutils installed? If so, did set PATH to point to the
binutils executable? Could you Try h8300-elf-ld --version and send me
the result?
Kazu Hirata
next reply other threads:[~2002-11-07 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 6:06 Kazu Hirata [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 4:11 kazu
2002-11-03 17:06 evanlanglois
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=20021107140605.9944.qmail@sources.redhat.com \
--to=kazu@cs.umass.edu \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).