device: 0.530
semantic: 0.220
graphic: 0.174
mistranslation: 0.129
vnc: 0.104
socket: 0.100
user-level: 0.096
boot: 0.091
PID: 0.076
network: 0.075
register: 0.073
debug: 0.072
architecture: 0.070
risc-v: 0.061
files: 0.061
ppc: 0.051
performance: 0.047
virtual: 0.047
arm: 0.046
permissions: 0.042
TCG: 0.040
VMM: 0.039
peripherals: 0.039
x86: 0.034
i386: 0.033
kernel: 0.022
assembly: 0.021
hypervisor: 0.020
KVM: 0.012

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.