other: 0.252
semantic: 0.179
device: 0.144
vnc: 0.062
graphic: 0.055
debug: 0.047
PID: 0.046
files: 0.043
permissions: 0.034
socket: 0.032
boot: 0.032
performance: 0.030
network: 0.028
KVM: 0.016
debug: 0.211
files: 0.210
other: 0.174
PID: 0.058
device: 0.058
semantic: 0.056
network: 0.046
boot: 0.040
performance: 0.037
socket: 0.028
permissions: 0.024
vnc: 0.024
graphic: 0.021
KVM: 0.013

Configure uses wrong libtool on Darwin

On Darwin/OS X, there are two versions of libtool: the GNU libtool, and Apple's libtool. Both are installed, but Apple's libtool (libtool) won't build libcacard that Qemu uses, but Gnu's libtool (glibtool) does. I get around using Apple's libtool by passing LIBTOOL=glibtool when configuring; unfortunately this variable isn't preserved so when Qemu's configure changes it's not passed. A simple switch in the configure script could check for Darwin, then if present, use glibtool. Or configure could check the features of libtool, see if they can build libcacard, then look for alternatives like glibtool. 

This bug was probably introduced when libcacard was added to Qemu, and is present in commit 93b6599734f81328ee3d608f57667742cafeea72.

Since libcacard is not longer part of QEMU, I assume this is not an issue anymore today. So can we close this bug nowadays?

Yes, libtool handling was removed entirely in commit e999ee443496b, so this bug is no longer present.