From: Ralf Baechle <ralf@linux-mips.org>
To: Mile Davidovic <mile.davidovic@micronasnit.com>
Cc: "'Linux/MIPS Development'" <linux-mips@linux-mips.org>
Subject: Re: Mips 4KEC
Date: Wed, 11 May 2005 15:27:07 +0100 [thread overview]
Message-ID: <20050511142707.GF6072@linux-mips.org> (raw)
In-Reply-To: <200505111424.j4BEOu1p017560@krt.neobee.net>
On Wed, May 11, 2005 at 04:20:53PM +0200, Mile Davidovic wrote:
> 1. I have question regarding toolchain, I use toolchain which came from
> uclibc buildroot
> application. Gcc version is 3.4.2, is it ok?
Yes.
> 2. I tried to use sde-lite 5.03 toolchain but this toolchain (sde-gcc)
> failed to build kernel.
> Please any comments regarding this issue?
> 3. I tried to remove optimization from kernel:
> I tried with googling but it seems that nobody faced similar problem? Is it
> possible to buidl kernel without optimization?
No. That's FAQ since 10 years.
Ralf
next prev parent reply other threads:[~2005-05-11 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-11 14:20 Mips 4KEC Mile Davidovic
2005-05-11 14:27 ` Ralf Baechle [this message]
2005-05-11 16:13 ` Nigel Stephens
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=20050511142707.GF6072@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=mile.davidovic@micronasnit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox