Hmm...
I confess that I did not track down the inner functionality of that
macro... so this is good new information and I will have to look elsewhere
to determine where the process is breaking. Curiously, the code used in
these autoconf tests compiles, links, and executes successfully on both the
native build system host and the test target system. Both machines support
priority-inheriting mutexes, mutex protocol specification, and robust
mutexes. However for some reason the autoconf process fails to recognize
this support.
Since my understanding was that any compilation during the bitbake build
was done for the target system unless it was specified that a native tool
was being built, I assumed that the AC_TRY_COMPILE process would be done
against the target libraries and headers. This should succeed since the
feature support in question is present in the target image - so I further
assumed the macro must be attempting to execute the code and evaluate a
runtime return value - which would be expected to fail as mentioned in my
previous email.
Given this new information, if the macro tests only the compilation success
and still fails despite the feature support being present then there must
be a failure to find the correct headers or compiler executables... so I
will explore this possibility. Thanks for your patience and your response
to my questions.
On Thu, Sep 4, 2014 at 5:13 AM, <[email protected]> wrote:
> Hi!
> > The autoconf scripts in 'ltp/testcases/realtime/m4/check.m4' evaluate
> > whether priority-inheriting mutexes and robust mutexes are supported on
> the
> > system for which the LTP realtime tests are being targeted. Portions of
> > the LTP realtime test code required to test these features on the target
> > are then conditionally included or excluded at compile time based on
> > autoconf results.
> >
> > To check these features, the autoconf scripts attempt to compile and then
> > execute initialization functions which rely on the features. Is this
> done
> > because the mere presence of the appropriate headers and protocol value
> > definitions, etc. is insufficient proof that the features are supported?
>
> Maybe I've overlooked something but all I see in the check.m4 file is
> AC_TRY_COMPILE() which should only try to run the code through the
> compile not even link it. At which point does the relatime configure
> execute the cross compiled binaries?
>
> --
> Cyril Hrubis
> [email protected]
>
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
