Summary: | Illegal Instruction on make {oldconfig,menuconfig} with sys-kernel/gentoo-sources on Via C3 Samuel 2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | R Bar-On <rb6> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED INVALID | ||
Severity: | major | CC: | jer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | strace make oldconfig |
Description
R Bar-On
2009-01-26 19:46:08 UTC
Created attachment 179802 [details]
strace make oldconfig
strace scripts/kconfig/conf arch/x86/Kconfig: execve("scripts/kconfig/conf", ["scripts/kconfig/conf", "arch/x86/Kconfig"], [/* 31 vars */]) = 0 brk(0) = 0x805a000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=22723, ...}) = 0 mmap2(NULL, 22723, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f94000 close(3) = 0 open("/lib/libncursesw.so.5", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\240\v\1\0004\0\0\0p"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=307288, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7f93000 mmap2(NULL, 312356, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7f46000 mmap2(0xb7f89000, 36864, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x42) = 0xb7f89000 mmap2(0xb7f92000, 1060, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f92000 close(3) = 0 open("/lib/libc.so.6", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0@a\1\0004\0\0\0\24"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=1200228, ...}) = 0 mmap2(NULL, 1205712, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7e1f000 mmap2(0xb7f40000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x121) = 0xb7f40000 mmap2(0xb7f43000, 9680, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f43000 close(3) = 0 open("/lib/libdl.so.2", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\n\0\0004\0\0\0,"..., 512) = 512 fstat64(3, {st_mode=S_IFREG|0755, st_size=9612, ...}) = 0 mmap2(NULL, 12412, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7e1b000 mmap2(0xb7e1d000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1) = 0xb7e1d000 close(3) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7e1a000 set_thread_area({entry_number:-1 -> 6, base_addr:0xb7e1a6c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 mprotect(0xb7e1d000, 4096, PROT_READ) = 0 mprotect(0xb7f40000, 8192, PROT_READ) = 0 mprotect(0xb7f89000, 32768, PROT_READ) = 0 mprotect(0x8057000, 4096, PROT_READ) = 0 mprotect(0xb7fb4000, 4096, PROT_READ) = 0 munmap(0xb7f94000, 22723) = 0 brk(0) = 0x805a000 brk(0x807b000) = 0x807b000 open("/usr/lib/locale/locale-archive", O_RDONLY|O_LARGEFILE) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=1520480, ...}) = 0 mmap2(NULL, 1520480, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7ca6000 close(3) = 0 open("arch/x86/Kconfig", O_RDONLY) = 3 uname({sys="Linux", node="gentoo-server", ...}) = 0 --- SIGILL (Illegal instruction) @ 0 (0) --- +++ killed by SIGILL +++ If this really is an i586 compatible chip, then your `uname -m' shouldn't be returning "i686" as the `emerge --info' suggests it does. You should be using a generic x86 CD and stage3 tarball instead of the i686 ones. I thought this might be the case. However, my CFLAGS and CHOST are not i686.... Can I solve this by rebuilding the toolchain (emerge -e system) followed by rebuilding the rest (emerge -e world), using the changing CHOST guide or do I really need a complete reinstall? (In reply to comment #4) > I thought this might be the case. However, my CFLAGS and CHOST are not > i686.... Changing a few variables around doesn't magically make previously compiled code refrain from issuing incompatible instructions. > Can I solve this by rebuilding the toolchain (emerge -e system) followed by > rebuilding the rest (emerge -e world), using the changing CHOST guide or do I > really need a complete reinstall? You hadn't come that far to begin with, apparently, so starting over is the best way to go. Do mind that re-emerging the toolchain would probably cause the same kinds of issues you're seeing now. Sorry to be a nuisance, but could you explain a little more please? Surely rebuilding the toolchain with correct parameters, followed by a complete rebuild would effectively do the same as a fresh install? If you don't mind, could you explain the differences? No, sorry. This is a bug tracker and not a support forum. And the changes you want to make will probably not work. Unpacking a proper stage3 would be best. If you really must go that experimental route, then try it on forums.gentoo.org. |