I'm not sure if this is a nettle component we should just disable (since a dependency chain of gnutls -> nettle -> openssl would obviously be undesirable) but in any case something is going wrong on the autobuilder: | gcc -I.. -I/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-multilib/build/build/tmp/work/x86_64-linux/nettle-native/2.7.1-r0/nettle-2.7.1 -isystem/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-multilib/build/build/tmp/sysroots/x86_64-linux/usr/include -DHAVE_CONFIG_H -isystem/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-multilib/build/build/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe -ggdb3 -Wno-pointer-sign -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wpointer-arith -Wbad-function-cast -Wnested-externs -fpic -c /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-multilib/build/build/tmp/work/x86_64-linux/nettle-native/2.7.1-r0/nettle-2.7.1/examples/next-prime.c && true | /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-multilib/build/build/tmp/work/x86_64-linux/nettle-native/2.7.1-r0/nettle-2.7.1/examples/nettle-openssl.c:40:25: fatal error: openssl/aes.h: No such file or directory | #include <openssl/aes.h> | ^ | compilation terminated. | Makefile:44: recipe for target 'nettle-openssl.o' failed | make[1]: *** [nettle-openssl.o] Error 1 Full log: https://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/81/steps/BuildImages_4/logs/stdio
I've tried to reproduce this on my localhost: with or without openssl(-native) built before nettle-native I cannot reproduce it. I had a look in configure: it checks for openssl/aes.h and if header is missing, it does not include openssl glue in benchmark program. I'll update this bug as soon as I find how to reproduce it.
You may not be able to reproduce it easily, but there is a clue there - if openssl/aes.h is there during configure and then not there during compile (which is possible since there's no dependency to ensure it's not in the middle of rebuilding OpenSSL at the same time) then this situation could happen. If this is indeed the issue I would suggest just forcing this particular functionality off, because adding a dependency on OpenSSL would be wrong in this case. Hopefully this is as simple as adding the appropriate configure argument.
Also a bug in the configure script might exists so maybe adding --disable-openssl will have any effect.
patch merged: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ebaf77dc730d2fdc58c06c16adf0f9ce474dbffc
Verified Cheers! Andra