Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Michael Dosser <mic@nethack.at>
To: linux-mips@linux-mips.org
Subject: mips64
Date: Wed, 20 Aug 2003 12:03:40 +0200	[thread overview]
Message-ID: <20030820100339.GO15525@nethack.at> (raw)

Hi,

I'm successfully running Debian/GNU Linux on a SGI Indy R4600PC@100Mhz
for over a year now. I'm very happy with the stability of Linux on that
machine. But since the machine is relatively slow (currently 30-35 
shell user continuosly connected), I bought an Indigo2 R4400SC@250Mhz.

I thought of putting a mips64 kernel on the new machine: Got the rpm's
from ftp.linux-mips.org, converted them with alien to debs and installed 
them on my quad xeon Debian box - checked out the linux source and 
started compiling:

# cvs -d :pserver:cvs@ftp.linux-mips.org:/home/cvs co -r linux_2_4 linux
# cd linux
# make ARCH=mips64 dep
# make ARCH=mips64 clean
# make ARCH=mips64 all

Error message with gcc version egcs-2.91.66 19990314 (egcs-1.1.2
release)

[...]
make[2]: Entering directory `/usr/local/src/mips/linux/arch/mips/math-emu'
mips64-linux-gcc -D__KERNEL__ -I/usr/local/src/mips/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -I /usr/local/src/mips/linux/include/asm/gcc -mabi=64 -G 0 -mno-abicalls -fno-pic -Wa,--trap -pipe -mcpu=r4600 -mips3 -Wa,-32 -Wa,-mgp64   -nostdinc -iwithprefix include -DKBUILD_BASENAME=cp1emu  -c -o cp1emu.o cp1emu.c
cp1emu.c: In function `fpu_emulator_cop1Handler':
cp1emu.c:1328: internal error--unrecognizable insn:
(insn 310 33 25 (set (reg:SI 159)
        (reg/v:DI 87)) -1 (insn_list:REG_DEP_ANTI 28 (insn_list 33 (nil)))
    (nil))
../../gcc/toplev.c:1367: Internal compiler error in function fatal_insn
make[2]: *** [cp1emu.o] Error 1
make[2]: Leaving directory `/usr/local/src/mips/linux/arch/mips/math-emu'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/local/src/mips/linux/arch/mips/math-emu'
make: *** [_dir_arch/mips/math-emu] Error 2
# 

Error with gcc version 2.95.4 20010319 (prerelease):

[...]
mips64-linux-ld --oformat elf32-tradbigmips   -r -o kernel.o sched.o
dma.o fork.o exec_domain.o panic.o printk.o module.o exit.o itimer.o
info.o time.o softirq.o resource.o sysctl.o acct.o capability.o ptrace.o
timer.o user.o signal.o sys.o kmod.o context.o ksyms.o
mips64-linux-ld: target elf32-tradbigmips not found
make[2]: *** [kernel.o] Error 1
make[2]: Leaving directory `/usr/local/src/mips/linux/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/local/src/mips/linux/kernel'
make: *** [_dir_kernel] Error 2
#

Ok, the latter seems to be related to objdump, right?
mips64-linux-objdump: supported targets: elf32-bigmips elf32-littlemips
elf64-bigmips elf64-littlemips ecoff-bigmips ecoff-littlemips
elf64-little elf64-big elf32-little elf32-big srec symbolsrec tekhex
binary ihex

The package on linux-mips.org seems not to be including
elf32-tradbigmips ...

Can somebody help me with this? Btw: same errors with co -r linux_2_4_21
...

Thank you,mic

-- 
> Please specifically define where data goes that is sent to /dev/null
[...]
Answer 2.  All the data goes into another dimension, and comes out of
/dev/random.            Stephen Montgomery-Smith on freebsd-hackers

             reply	other threads:[~2003-08-20 10:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-20 10:03 Michael Dosser [this message]
2003-08-20 10:15 ` mips64 Thiemo Seufer
2003-08-20 10:23   ` mips64 Ladislav Michl
2003-08-20 12:08   ` mips64 Michael Dosser
  -- strict thread matches above, loose matches on Subject: below --
1999-08-22 12:15 MIPS64 Ralf Baechle
     [not found] ` <00ee01beece1$18b16bf0$b8119526@ltc.com>
1999-08-22 21:17   ` MIPS64 Ralf Baechle
     [not found]     ` <012601beeceb$6a4d19a0$b8119526@ltc.com>
1999-08-22 22:28       ` MIPS64 Ralf Baechle
1999-08-23 14:28 ` MIPS64 Andreas Jaeger
1999-08-23 22:09   ` MIPS64 Ralf Baechle
     [not found] ` <19990928163615.H25202@anxur.fi.muni.cz>
     [not found]   ` <19990929160211.B21646@uni-koblenz.de>
     [not found]     ` <19991005132552.K18469@gryf.fi.muni.cz>
     [not found]       ` <19991006000724.B18573@uni-koblenz.de>
     [not found]         ` <19991007142022.O18469@gryf.fi.muni.cz>
1999-10-10  2:13           ` MIPS64 Ralf Baechle
     [not found]             ` <19991011010723.G981@uni-koblenz.de>
1999-11-01 16:43               ` MIPS64 Ludek Finstrle

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=20030820100339.GO15525@nethack.at \
    --to=mic@nethack.at \
    --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