From: Randy Witt <randy.e.witt@linux.intel.com>
To: linux-rt-users@vger.kernel.org
Subject: rt-tests v1.9 fails to compile on architectures that aren't x86_64, i386 or PPC64
Date: Mon, 28 Sep 2020 15:14:23 -0700 [thread overview]
Message-ID: <62cb6195-7116-db1d-2af2-264dbd854ddb@linux.intel.com> (raw)
With the addition of the oslat test in v1.9, "make" with no arguments will fail
on any architecture that isn't x86_64, i386 or PPC64. This is due to the #error
added here
https://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git/tree/src/oslat/oslat.c?h=v1.9#n72.
Since there is no build time configuration to turn off particular tests, is the
expected workflow to specify the set of desired tests as make arguments?
In the absence of some sort of configure script, should there be a variable that
allows for tests to be removed from the set of TARGETS?
next reply other threads:[~2020-09-28 23:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 22:14 Randy Witt [this message]
2020-09-30 15:45 ` rt-tests v1.9 fails to compile on architectures that aren't x86_64, i386 or PPC64 Peter Xu
2020-10-01 19:00 ` Randy Witt
2020-10-01 20:05 ` Peter Xu
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=62cb6195-7116-db1d-2af2-264dbd854ddb@linux.intel.com \
--to=randy.e.witt@linux.intel.com \
--cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).