From: David Howells <dhowells@redhat.com>
To: Jan Dittmer <jan.dittmer@gmail.com>
Cc: dhowells@redhat.com, linux-am33-list@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Linux-am33-list] Cross-Compiling mn10300: Assembler messages: junk at end of line: 0
Date: Fri, 15 Feb 2008 13:25:24 +0000 [thread overview]
Message-ID: <22098.1203081924@redhat.com> (raw)
In-Reply-To: <47B490A8.3050500@gmail.com>
Jan Dittmer <jan.dittmer@gmail.com> wrote:
> + make ARCH=mn10300 HOSTCC=gcc-4.0 CROSS_COMPILE=mn10300-elf-
> CROSS32_COMPILE= O=../2.6.25-rc1-mn10300/
Hmmm... There seems to be some confusion somewhere, probably because the
documentation there doesn't say which compiler you should use for what. Can
you try this toolchain instead:
i686-pc-linux-gnulibc2.3-x-am33_2.0-linux-gnu.tar.bz2
rather than the:
i686-pc-linux-gnulibc2.3-x-mn10300-elf.tar.bz2
in the location:
ftp://ftp.redhat.com/pub/redhat/gnupro/AM33/am33-04r2-5/tools/
Note that the MN10300 arch needs some patches to get it to compile due to some
changes that Linus merged that weren't in the -mm tree.
David
prev parent reply other threads:[~2008-02-15 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 19:04 Cross-Compiling mn10300: Assembler messages: junk at end of line: 0 Jan Dittmer
2008-02-15 13:25 ` David Howells [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=22098.1203081924@redhat.com \
--to=dhowells@redhat.com \
--cc=jan.dittmer@gmail.com \
--cc=linux-am33-list@redhat.com \
--cc=linux-kernel@vger.kernel.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