From: william <william@zh.t2-design.com>
To: Ryan Murray <rmurray@cyberhqz.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: native gcc-3.0.1?
Date: Thu, 20 Sep 2001 18:00:39 +0800 [thread overview]
Message-ID: <3BA9BE47.BEF47A87@zh.t2-design.com> (raw)
In-Reply-To: 20010919230953.B6044@cyberhqz.com
Ryan Murray wrote:
> On Thu, Sep 20, 2001 at 01:57:42AM -0400, Jim Paris wrote:
> > Does anyone have gcc-3.0.1 built as a native MIPS compiler?
>
> Debian built 3.0.1 natively...
>
> > It could also be that gcc-3.0.1 is simply broken when running natively
> > on MIPS. Has anyone done this? Any luck?
>
> When that was the version in Debian, it did work.
>
> > anyone has built gcc-3.0 or gcc-3.0.1 natively on MIPS, can you send
> > me the config.cache from your build?
>
> I don't have that around anymore, but I can send you the config.cache from
> a build of a 3.0.2 CVS snapshot...
>
> --
> Ryan Murray, Debian Developer (rmurray@cyberhqz.com, rmurray@debian.org)
> The opinions expressed here are my own.
>
> ------------------------------------------------------------------------
> Part 1.2Type: application/pgp-signature
Hi,
Just, I use GCC-3.0.1 to compile Linux kernel,except
ramdisk.o,everything seems fine.about ramdisk.o
because GCC-3.0.1 can't suppor failed to merge target specific data of file
../boot/ramdisk.ot ecoff-littlemips target.so I modified it as
elf32-littlemips,but when linking, compiler told me failed to merge specific
data of file ramdisk.o,from the output compiler message,it says ISA
mismatch(-mips1) with previous modules(--mips3) and used different
e_flags(0x0) fields than previous modules(0x100).What's wrong with it?
Best regards
william 20/9/2001
prev parent reply other threads:[~2001-09-20 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 5:57 native gcc-3.0.1? Jim Paris
2001-09-20 6:09 ` Ryan Murray
2001-09-20 10:00 ` william [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=3BA9BE47.BEF47A87@zh.t2-design.com \
--to=william@zh.t2-design.com \
--cc=linux-mips@oss.sgi.com \
--cc=rmurray@cyberhqz.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.