Using gcc-4.7.1 and amd64 (don't know if it applies to other arches), makes it not compile (build log and emerge --info attached after) Reproducible: Always
Created attachment 318584 [details] build log
Created attachment 318586 [details] merge --info
I got the same with gcc 4.6.2 on x86. It seems that libfprint doesn't like the new libusbx.
There is a patch for libfprint for this here: "https://bugs.archlinux.org/task/30721". Could anyone please apply it to portage? It should fix the problem. The thing is that the enum fpi_log_level from libfprint/fp_internal.h defines the same constants as enum usbi_log_level from the /usr/include/libusb-1.0/libusb.h from libusbx, so they just need to be renamed differently within the libfprint.
Created attachment 322681 [details, diff] Fixes the libfprint variable collision (with libusbx) problem by renaming LOG_LEVEL_* constants to FPRINT_LOG_LEVEL_* This is just the patch (not mine) from the URL referred to in the previous message reposted here. It fixes the problem described above. Please apply.
Thanks, I look into it later.
(In reply to comment #6) > Thanks, I look into it later. Hi, I'm libusb upstream. I'll try to clean up a bit after the mess that is libusbx. Some versions ago they polluted the global namespace with what used to be library-internal identifiers, and since libfprint originated from the same author the two libraries used the same identifiers. The libusbx people fixed their error in later releases. libusb-1.0.9 of course does not have the error in the first place. I would close this bug. I think it's also a duplicate of another one, but in any case older versions of libusbx caused the problem but are no longer in portage.
closing since only latest libusbx is left in portage
