Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Fuxin Zhang <fxzhang@ict.ac.cn>
To: remex_cao@sjtu.edu.cn
Cc: linux-mips@linux-mips.org
Subject: Re:
Date: Wed, 14 Apr 2004 14:34:35 -0400	[thread overview]
Message-ID: <407D843B.1070405@ict.ac.cn> (raw)
In-Reply-To: <20040414060301.F2F297B01A5@mx1.sjtu.edu.cn>



caoxiang wrote:

>Greetings
>
>I've encountered a problem when I am porting linux 2.4.3 to the SEAD-2 board.
>
>The tool-chain I used include:
>
>gcc-mipsel-linux-2.95.4
>
>gcc-mips-linux-2.95.4
>
>binutils-mipsel-linux-2.13.1
>
>An error occured like that When I make the kernel:
>
>mipsel-linux-ld -static -G 0 -T arch/mips/ld.script arch/mips/kernel/head.o arch/mips/kernel/init_task.o init/main.o init/version.o \
>        --start-group \
>        arch/mips/kernel/kernel.o arch/mips/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o arch/mips/math-emu/fpu_emulator.o \
>        drivers/block/block.o drivers/char/char.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o  drivers/parport/driver.o drivers/usb/usbdrv.o \
>        net/network.o \
>        arch/mips/lib/lib.a /usr/local/0_mips/linux-2.4.3/lib/lib.a arch/mips/mips-boards/sead/sead.o arch/mips/mips-
> boards/generic/mipsboards.o \
>        --end-group \
>        -o vmlinux
>mipsel-linux-ld: target elf32-littlemips not found
>  
>
change elf32-littlemips in arch/mips/ld.script to elf32-tradlittlemips

use mipsel-linux-ld --verbose to show supported OUTPUT_FORMAT of your ld

>make: *** [vmlinux] Error 1
>
>As I change to big endian the problem still exists. Shall I apply some patch?
>
>Thanks for help.
>
>remex
>

  reply	other threads:[~2004-04-14  6:36 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14  6:05 caoxiang
2004-04-14 18:34 ` Fuxin Zhang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-17  9:09 Paulo Miguel Almeida
2024-10-17  9:12 ` Paulo Miguel Almeida
2020-05-06  5:52 Jiaxun Yang
2020-05-06 17:17 ` Nick Desaulniers
2017-11-13 14:55 Re: Amos Kalonzo
2017-11-13 14:55 ` Re: Amos Kalonzo
2017-02-23 15:09 Qin's Yanjun
2017-02-23 15:09 ` RE: Qin's Yanjun
2010-06-11 14:06 Jabir M
2010-06-11 14:32 ` Manuel Lauss
2010-06-11 17:06   ` Re: David Daney
2010-06-11 17:33     ` Re: Kevin D. Kissell
2010-06-11 18:28       ` Re: Manuel Lauss
2006-01-04 12:50 Sathesh Babu Edara
2006-01-04 13:06 ` Kevin D. Kissell
2006-01-09  7:43   ` Sathesh Babu Edara
2006-01-09  7:43     ` RE: Sathesh Babu Edara
2006-01-09  9:00     ` Kevin D. Kissell
2006-01-09  9:00       ` Re: Kevin D. Kissell
2005-04-28 21:30 Raj Palani
2005-04-28 19:15 Bryan Althouse
2005-05-04 13:55 ` Alex Gonzalez
2005-05-04 14:22   ` Bryan Althouse
2005-05-04 14:22     ` RE: Bryan Althouse
2005-05-04 16:42     ` Ralf Baechle
2005-05-05 14:55   ` Re: Ralf Baechle
2005-05-05 15:08     ` Bryan Althouse
2005-05-05 15:08       ` RE: Bryan Althouse
2005-05-05 15:11       ` Ralf Baechle
2005-05-05 15:57     ` Re: Geert Uytterhoeven
2005-05-05 17:13     ` Re: Christoph Hellwig
2004-11-16  6:09 Re: Fuxin Zhang
2004-11-14  1:32 Re: Fuxin Zhang
2004-11-13 14:47 Re: macrohat
2004-09-03  8:57 xuhaoz
2004-09-03 21:47 ` Fuxin Zhang
2004-08-27  1:49 Re: bel racu
2003-11-01  1:38 Lyle Bainbridge
2003-11-03 18:14 ` Pete Popov

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=407D843B.1070405@ict.ac.cn \
    --to=fxzhang@ict.ac.cn \
    --cc=linux-mips@linux-mips.org \
    --cc=remex_cao@sjtu.edu.cn \
    /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