From: "T. P. Saravanan" <sara@procsys.com>
To: linux-mips@linux-mips.org
Subject: mips linux glibc-2.3.3 build - opcode not supported problem
Date: Thu, 30 Sep 2004 11:12:42 +0530 [thread overview]
Message-ID: <415B9CD2.3070607@procsys.com> (raw)
Hi,
I hope it is OK to post linux mips glibc build problems here. If not,
please let me
know an appropriate forum.
---
Host type: mipsel-unknown-linux-gnu
System: Linux eyeore 2.4.25 #20 Wed Sep 29 09:01:29 IST 2004 mips unknown
Architecture: mips
Addons: linuxthreads
Build CFLAGS: -g -O2
Build CC: gcc
Compiler version: 3.4.2
Kernel headers: 2.4.25
Symbol versioning: yes
Build static: yes
Build shared: yes
Build pic-default: yes
Build profile: yes
Build omitfp: no
Build bounded: no
Build static-nss: no
sara@eyeore:~/tmp$ cat /proc/cpuinfo
system type : ITE QED-4N-S01B
processor : 0
cpu model : Nevada V3.1 FPU V3.0
BogoMIPS : 299.00
wait instruction : yes
microsecond timers : yes
tlb_entries : 48
extra interrupt vector : yes
hardware watchpoint : no
VCED exceptions : not available
VCEI exceptions : not available
sara@eyeore:~/tmp$
This is how the build dies:
.
.
.
gcc -mabi=32 ../sysdeps/unix/sysv/linux/mips/_test_and_set.c -c
-std=gnu99 -O2 -Wall -Winline -Wstrict-prototypes -Wwrite-strings
-g -I../include -I. -I/home/sara/build/glibc/objdir/misc -I..
-I../libio -I/home/sara/build/glibc/objdir -I../sysdeps/mips/elf
-I../linuxthreads/sysdeps/unix/sysv/linux/mips
-I../linuxthreads/sysdeps/unix/sysv/linux
-I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread
-I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix
-I../linuxthreads/sysdeps/mips -I../sysdeps/unix/sysv/linux/mips/mips32
-I../sysdeps/unix/sysv/linux/mips -I../sysdeps/unix/sysv/linux
-I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman
-I../sysdeps/unix/inet -I../sysdeps/unix/sysv
-I../sysdeps/unix/mips/mips32 -I../sysdeps/unix/mips -I../sysdeps/unix
-I../sysdeps/posix -I../sysdeps/mips/mips32 -I../sysdeps/mips
-I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754/dbl-64
-I../sysdeps/wordsize-32 -I../sysdeps/mips/fpu -I../sysdeps/ieee754
-I../sysdeps/generic/elf -I../sysdeps/generic -nostdinc -isystem
/home/sara/usr/local/lib/gcc/mipsel-unknown-linux-gnu/3.4.2/include
-isystem /home/sara/build/linux/linux-2.4.25mips/include
-D_LIBC_REENTRANT -include ../include/libc-symbols.h -DPIC -o
/home/sara/build/glibc/objdir/misc/_test_and_set.o -MD -MP -MF
/home/sara/build/glibc/objdir/misc/_test_and_set.o.dt
/tmp/ccDGPHmY.s: Assembler messages:
/tmp/ccDGPHmY.s:28: Error: opcode not supported on this processor: mips1
(mips1) `ll $2,0($4)'
/tmp/ccDGPHmY.s:31: Error: opcode not supported on this processor: mips1
(mips1) `sc $3,0($4)'
make[2]: *** [/home/sara/build/glibc/objdir/misc/_test_and_set.o] Error 1
make[2]: Leaving directory `/home/sara/build/glibc/glibc-2.3.3/misc'
make[1]: *** [misc/subdir_lib] Error 2
make[1]: Leaving directory `/home/sara/build/glibc/glibc-2.3.3'
make: *** [all] Error 2
sara@eyeore:~/build/glibc/objdir$
The problem seems to go away if I put CFLAGS="-mips4 -O2 -g". Is it OK
to do this?
Why did gcc/gas fail to use -mips4 opcodes by default?
-Saravanan
next reply other threads:[~2004-09-30 5:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 5:42 T. P. Saravanan [this message]
[not found] <026b01c4a6d5$179b11e0$1701a8c0@vmbservice.ru>
2004-10-04 5:19 ` mips linux glibc-2.3.3 build - opcode not supported problem T. P. Saravanan
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=415B9CD2.3070607@procsys.com \
--to=sara@procsys.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 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.