<div dir="ltr">Thanks to Randy Witt for a patch which resolves this issue. Randy wrote: "I looked at the configure logs on an x86 build and saw the same problem.
By default the autotools.bbclass searches for m4 macros in the source
tree. But it searches a depth that is lower than the directory depth of
the location of testcases/realtime/m4. That seems to be causing some of
the macros to be missing and falsely causing features to be missing." I believe he will be submitting the patch soon, but am including a link below for reference:<br><br><a href="https://mail.google.com/mail/u/0/?ui=2&ik=670054f0eb&view=att&th=14847f46218cf453&attid=0.1&disp=safe&zw">0001-ltp-Add-additional-m4-path-to-autoconf.patch</a><br>
</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 5, 2014 at 3:36 PM, Gary Robertson <span dir="ltr"><<a href="mailto:gary.robertson@linaro.org" target="_blank">gary.robertson@linaro.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Dear OE developers,<br></div><div><br></div>Linaro Networking Group is building root filesystem images containing the LTP test suite, using the current recipe at openembedded-core/meta/recipes-extended/ltp/<a href="http://ltp_20140422.bb" target="_blank">ltp_20140422.bb</a>. This build uses autoconf to probe mutex feature support for protocol specification, priority inheritance, and robust mutexes. The macros used for this can be found in ltp/testcases/realtime/m4/check.m4 from the LTP git repository.<br><br></div>We are cross-building for the armv7a architecture using the machine definition found in meta-linaro/meta-linaro/conf/machine/genericarmv7a.conf. The development host platform is an Ubuntu 12.04 x86_64 platform with all software kept regularly updated from the Ubuntu repositories.<br><br></div>The macros in check.m4 use the AC_TRY_COMPILE function macro to attempt compilation of POSIX function calls utilizing the features being probed - such that if the compilation fails the features are deemed to be unsupported... and if compilation succeeds the features are deemed supported.<br><br></div>Native compilation of the same code used in the probes, and execution of the resulting program - shows support for all the probed mutex features on both the development host as well as the armv7a target platform... that is when this probe code is built on either the host or target machine and then executed in that environment... so support is there in both environments.<br><br></div>Despite the presence of this support the AC_TRY_COMPILE macro is indicating a lack of support for the probed features during the cross-build process.<br><br>I am not personally familiar with the detailed function of the autoconf macros, and I can find no documentation about how OE interacts with those macros in order to coerce them into configuring for the target machine in a cross-build environment... so I am hoping the autoconf experts at OE can shed some light on this and at least provide some clues as to where to look for the problem and possible resolution. Any insight you can provide in this matter would be appreciated.<br><div><div><div><br></div><div>Gary Robertson<br><br></div><div>Real-time engineer, Linaro Networking Group<br></div><div><br></div></div></div></div>
</blockquote></div><br></div>