Bug 11951 - (refkit) tpm-tools-native-1.3.9.1 compile error
Summary: (refkit) tpm-tools-native-1.3.9.1 compile error
Status: RESOLVED OBSOLETE
Alias: None
Product: IoT Reference OS Kit
Classification: Yocto Project Subprojects
Component: intel-iot-refkit-security (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.5
Assignee: Mikko Ylinen
QA Contact: yeoh ee peng
URL:
Whiteboard:
Depends on: 11950
Blocks:
  Show dependency tree
 
Reported: 2017-08-18 16:34 UTC by Juro Bystricky
Modified: 2017-11-14 13:04 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Juro Bystricky 2017-08-18 16:34:25 UTC 
A seen in Autobuilder:
https://autobuilder.yocto.io/builders/nightly-refkit/builds/122/steps/BuildImages/logs/stdio

Relevant part:

ERROR: tpm-tools-native-1.3.9.1+gitAUTOINC+5c5126bedf-r0 do_compile: oe_runmake failed
ERROR: tpm-tools-native-1.3.9.1+gitAUTOINC+5c5126bedf-r0 do_compile: Function failed: do_compile (log file is located at /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-refkit/build/build/tmp-glibc/work/x86_64-linux/tpm-tools-native/1.3.9.1+gitAUTOINC+5c5126bedf-r0/temp/log.do_compile.946)
ERROR: Logfile of failure stored in: /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-refkit/build/build/tmp-glibc/work/x86_64-linux/tpm-tools-native/1.3.9.1+gitAUTOINC+5c5126bedf-r0/temp/log.do_compile.946
Log data follows:
...

tpm_extendpcr.c: In function ‘main’:
| tpm_extendpcr.c:139:14: error: storage size of ‘ctx’ isn’t known
|    EVP_MD_CTX ctx;
|               ^~~
| tpm_extendpcr.c:139:14: warning: unused variable ‘ctx’ [-Wunused-variable]
| make[3]: *** [Makefile:472: tpm_extendpcr.o] Error 1
Comment 1 Mikko Ylinen 2017-08-24 03:19:12 UTC 
Same root cause and resolution as in bug #11950
Comment 2 Richard Purdie 2017-08-24 14:44:05 UTC 
We will end up moving to 1.1 so I think this needs to stay open to remind us this will need fixing eventually
Comment 3 Mikko Ylinen 2017-11-14 13:04:14 UTC 
Oe-core went back to openssl 1.0 and no plans to move to 1.1 just yet. Closing as obsolete for now.