Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ulrich Eckhardt <eckhardt@satorlaser.com>
To: linux-mips@linux-mips.org
Subject: Re: crosscompiler
Date: Tue, 17 May 2005 09:14:48 +0200	[thread overview]
Message-ID: <200505170914.48879.eckhardt@satorlaser.com> (raw)
In-Reply-To: <20050515125247.7596.fh034.wm@smtp.sc0.cp.net>

neoxx@canada.com wrote:
> I wanna set up a crosscompiler on my intel machine (
> using debian woody ) in order to cross-compile a
> self-written kernel ( no Linux/Mips ) for a MIPS 4kc (
> little endian ) CPU.

I'm using Debian/testing here and roughly followed
http://people.debian.org/~debacle/cross.html in order to get a working system. 
Almost no problems encountered.

> Can I alternatively use
> the mipsel-linux-gcc for the kernel ( I'm not quite
> sure what sort of compiler that is... )

mips= for MIPS
el= endianess little

IOW, this is precisely what I got from installing the crosscompiler and 
probably what you want. In order to compile non-Linux programs (i.e. programs 
launched directly from YAMON) I used these 
  CFLAGS += -Wall -mips32 -fno-builtin -mno-abicalls -fno-pic -GO -O2
though some of them might be redundant/unnecessary - I just tried combinations 
until it worked.

hth

Uli

  reply	other threads:[~2005-05-17  7:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-15 12:52 crosscompiler neoxx
2005-05-17  7:14 ` Ulrich Eckhardt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-11 13:26 Crosscompiler Carsten Langgaard
2000-12-12  4:07 ` Crosscompiler Ralf Baechle
2000-12-12  9:33   ` Crosscompiler Carsten Langgaard
2000-10-17 13:55 CrossCompiler Nicu Popovici
2000-10-17 14:30 ` CrossCompiler Steve Kranz
2000-10-17 15:20   ` CrossCompiler Keith M Wesolowski
1999-08-30 13:44 crosscompiler Thomas Berg
1999-08-30 13:44 ` crosscompiler Thomas Berg

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=200505170914.48879.eckhardt@satorlaser.com \
    --to=eckhardt@satorlaser.com \
    --cc=linux-mips@linux-mips.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