All of lore.kernel.org
 help / color / mirror / Atom feed
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: Toolchain question
Date: Mon, 11 Apr 2005 14:38:41 +0100	[thread overview]
Message-ID: <20050411133841.GX7038@linux-mips.org> (raw)
In-Reply-To: <200504111014.j3BADt1p023510@krt.neobee.net>

On Mon, Apr 11, 2005 at 12:13:50PM +0200, Mile Davidovic wrote:
> From:	"Mile Davidovic" <mile.davidovic@micronasnit.com>
> To:	"'Linux/MIPS Development'" <linux-mips@linux-mips.org>
> Subject: Toolchain question
> Date:	Mon, 11 Apr 2005 12:13:50 +0200
> Content-Type: text/plain;
> 	charset="iso-8859-2"
> 
> Hello all
> I would like to port board (with MIPS 4kec) to latest linux 2.6 kernel.
> Using porting guide 
> from (http://www.linux-mips.org/wiki/index.php/Porting) I successfully made
> console and
> serial driver. But problem appears with first printk (in start_kernel) I got
> exception.  
> 
> I used toolchain which uclibc buildroot script produced (gcc-3.4.2,
> binutils-2.15.91.0.2),
> and I am not sure is this correct combination.
> 
> >From 
> http://www.linux-mips.org/wiki/index.php/Toolchains I saw that next
> recommendations:
> 1. SDE MIPS - unfortunately this is 2.9x compiler.

Which should be perfectly find for the kernel.  And no, SDE isn't really
a 2.96-based compiler with _vastly_ improved code generation for MIPS
processors.

Less than a week ago SDE 5 was released which is based on gcc 3.4 and
similarly contains a large number of mostly MIPS-specific improvments.

> 2. Mr. Rozycki offer only mipsel toolchain

Recompiling is easy.

> 3. Mr. Kegel's crosstool but from
> http://kegel.com/crosstool/crosstool-0.31/buildlogs/ it seems that 
> this toolchain is not good for MIPS.

Plenty of success reports to this list contradict it.

> 4. Toolchain from ucLibc, I tried but I have trouble with.

No idea about this one.

> So my question: which toolchains I have to use? 

Since you have problems with all of these you may want to describe those ...

  Ralf

  reply	other threads:[~2005-04-11 13:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11 10:13 Toolchain question Mile Davidovic
2005-04-11 10:13 ` Mile Davidovic
2005-04-11 13:38 ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-12  4:59 Nori, Soma Sekhar
2005-04-12 12:07 ` Ralf Baechle
2002-03-17 20:34 Jan-Benedict Glaw
2002-03-18 15:42 ` Johannes Stezenbach
2002-03-18 15:47   ` Geert Uytterhoeven
2002-03-18 16:02     ` Johannes Stezenbach
2002-02-21 12:32 Jan-Benedict Glaw

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=20050411133841.GX7038@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 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.