$ echo '#include "gpgme.h"' > test.c && gcc test.c In file included from test.c:1:0: /usr/include/gpgme.h:14:24: fatal error: gpgme-i386.h: No such file or directory compilation terminated. $ rpm -qf /usr/include/gpgme.h gpgme-devel-1.3.0-6.fc17.i686 $ rpm -qlf /usr/include/gpgme.h|grep include /usr/include/gpgme-i686.h /usr/include/gpgme.h $ grep i.86 /usr/include/gpgme.h #if defined(__i386__) #include "gpgme-i386.h" Both __i386 and __i686__ is defined. Patching gpgme.h so it starts with a 686 sections brings it one step further but fails with /usr/include/gpgme-i686.h:95:2: error: #error GPGME was compiled with _FILE_OFFSET_BITS = 64, please see the section "Largefile support (LFS)" in the GPGME manual. I guess this problem might cause some FTBFS packages on i686.
OK, seen similar issues on other multilib hacks, I can apply the same fix here.
Fwiw, the latter problem is a separate one, in that apps that use gpgme are expected to be built using the same value of _FILE_OFFSET_BITS as gpgme was built with.
Try out this build: http://koji.fedoraproject.org/koji/taskinfo?taskID=4013881
Yes, that works for me. (Except for the LFS issue which probably is caused by package I was building - bazaar-1.4.2-14 (without docs) resurrected from the land of the orphans. Brutally and naively removing the warning from gpgme-32.h worked good enough for this experiment.)
gpgme-1.3.0-8.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2012-1726/gpgme-1.3.0-8.fc17
Package gpgme-1.3.0-8.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gpgme-1.3.0-8.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-1726/gpgme-1.3.0-8.fc17 then log in and leave karma (feedback).
gpgme-1.3.0-8.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.