From: chrubis@suse.cz
To: Gary Robertson <gary.robertson@linaro.org>
Cc: ltp-list <ltp-list@lists.sourceforge.net>,
Mike Holmes <mike.holmes@linaro.org>
Subject: Re: [LTP] [RFC] Realtime tests - autoconf problems in OpenEmbedded cross-build environment
Date: Thu, 4 Sep 2014 12:13:37 +0200 [thread overview]
Message-ID: <20140904101337.GA3151@rei.suse.cz> (raw)
In-Reply-To: <CAF7YWnxMVXpKKTbB3B4Sjqwp5K=u543PVbUBEy6jFGeq6YWkVw@mail.gmail.com>
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
chrubis@suse.cz
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-09-04 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 19:58 [LTP] [RFC] Realtime tests - autoconf problems in OpenEmbedded cross-build environment Gary Robertson
2014-09-04 10:13 ` chrubis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140904101337.GA3151@rei.suse.cz \
--to=chrubis@suse.cz \
--cc=gary.robertson@linaro.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=mike.holmes@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox