On Mon, Jul 16, 2012 at 2:37 PM, X O <bexoff@xxxxxxxxx> wrote: > Hello, > > I suspect upgrading my system to glibc-2.15 was a mistake. It seems to > be qemu-1.0.1, and latter versions including qemu-1.1.1, can't be > compiled anymore. Yes, I did search around and that led me to glibc, > resp. http://sourceware.org/ml/libc-ports/2011-08/msg00019.html > > Please, could somebody confirm or deny the following error is thanks > to glibc-2.15? > Is there a way to compile qemu with glibc-2.15? > Or is my system broken? > > ~~~ > CC i386-linux-user/syscall.o > /tmp/qemu-1.1.1/linux-user/syscall.c: In function 'sys_getdents': > /tmp/qemu-1.1.1/linux-user/syscall.c:217:1: error: '__NR_getdents' > undeclared (first use in this function) > /tmp/qemu-1.1.1/linux-user/syscall.c:217:1: note: each undeclared > identifier is reported only once for each function it appears in > /tmp/qemu-1.1.1/linux-user/syscall.c: In function '_llseek': > /tmp/qemu-1.1.1/linux-user/syscall.c:224:1: error: '__NR_lseek' > undeclared (first use in this function) > /tmp/qemu-1.1.1/linux-user/syscall.c: At top level: > /tmp/qemu-1.1.1/linux-user/syscall.c:358:12: warning: 'sys_futimesat' > defined but not used [-Wunused-function] > /tmp/qemu-1.1.1/linux-user/syscall.c: In function '_llseek': > /tmp/qemu-1.1.1/linux-user/syscall.c:223:1: warning: control reaches > end of non-void function [-Wreturn-type] > /tmp/qemu-1.1.1/linux-user/syscall.c: In function 'sys_getdents': > /tmp/qemu-1.1.1/linux-user/syscall.c:217:1: warning: control reaches > end of non-void function [-Wreturn-type] > ~~~ > > Thanks, > bexoff I meant to sent this out as soon as I found out, but it seems I didn't. Yeah, my system was broken, resp. /usr/include/ was. As soon as I had qemu back up, I put some time and effort to find out "why". Conclusion is - qemu-1.1.1 can be compiled just fine with glibc-2.15 and on x86_64. Sorry for inconvenience and thanks for all help. -- bexoff -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
