> It fails some other way ): > > $ make V=1 > gcc -m64 -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 > -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef > -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing > -fstack-protector-all -Wendif-labels -Wmissing-include-dirs -Wempty-body > -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self > -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition > -Wtype-limits -I../linux-headers -I.. > -I/home/jcmvbkbc/ws/m/awt/emu/xtensa/qemu/target-i386 -DNEED_CPU_H -pthread > -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include > -I/home/jcmvbkbc/ws/m/awt/emu/xtensa/qemu/linux-user/x86_64 > -I/home/jcmvbkbc/ws/m/awt/emu/xtensa/qemu/linux-user -O2 -g > -Wl,--warn-common -m64 -static -g -Wl,-T../config-host.ld > -Wl,-T,/home/jcmvbkbc/ws/m/awt/emu/xtensa/qemu/x86_64.ld -o qemu-x86_64 > ../libdis-user/i386-dis.o ../libuser/cache-utils.o ../libuser/cutils.o > ../libuser/envlist.o ../libuser/host-utils.o ../libuser/path.o > ../libuser/tcg-runtime.o ../libuser/trace.o ../libuser/trace/control.o > ../libuser/trace/default.o cpu-exec.o cpu-uname.o cpuid.o disas.o elfload.o > exec.o fpu/softfloat.o gdbstub.o helper.o ioport-user.o linuxload.o main.o > mmap.o op_helper.o osdep.o oslib-posix.o qemu-thread-posix.o signal.o > strace.o syscall.o tcg/optimize.o tcg/tcg.o thunk.o translate-all.o > translate.o uaccess.o user-exec.o -lrt -pthread -pthread -lgthread-2.0 -lrt > -lglib-2.0 -lm > > /usr/lib/gcc/x86_64-redhat-linux/4.6.1/../../../../lib64/libglib-2.0.a(gmem.o):(.note.stapsdt+0x24): > undefined reference to `glib_mem__alloc_semaphore' > /usr/lib/gcc/x86_64-redhat-linux/4.6.1/../../../../lib64/libglib-2.0.a(gmem.o):(.note.stapsdt+0x7c): > undefined reference to `glib_mem__alloc_semaphore' > /usr/lib/gcc/x86_64-redhat-linux/4.6.1/../../../../lib64/libglib-2.0.a(gmem.o):(.note.stapsdt+0xd0): > undefined reference to `glib_mem__alloc_semaphore' ...
It appears to be glib2 issue: https://bugzilla.gnome.org/show_bug.cgi?id=654078 In the latest F15 it's not fixed. Mr-4, probably you will not escape re-compiling, if not even patching glib2. Thanks. -- Max
