something i just noticed, rbtree.o is built in the kernel directory:
CC ../../lib/rbtree.o
that's Not Nice (tm) (we should never modify the kernel's objects) and it can
also cause problems like this when having a 32-bit tree built already:
/usr/bin/ld: i386 architecture of input file `../../lib/rbtree.o' is
incompatible with i386:x86-64 output
collect2: ld returned 1 exit status
Is there a reason why kvm does not do what perf does and build its own
rbtree.o?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
