Description of problem:
Random123's features/gccfeatures.h header (included from threefry.h via features/compilerfeatures.h) doesn't allow compilation on architectures other than x86 and ppc, but the package is noarch.

Version-Release number of selected component (if applicable):
1.08-4.fc24

How reproducible:
Always

Steps to Reproduce:
1. try to compile a simple program with
   #include <Random123/threefry.h>
   using gcc on ARM (it happened to me while compiling gromacs on ARM)

Actual results:
In file included from /usr/include/Random123/features/compilerfeatures.h:211:0,
                 from /usr/include/Random123/threefry.h:34,
                 from /builddir/build/BUILD/gromacs-5.1.2/src/gromacs/random/random.cpp:48:
/usr/include/Random123/features/gccfeatures.h:38:4: error: #error "This code has only been tested on x86 and powerpc platforms."
 #  error "This code has only been tested on x86 and powerpc platforms."
    ^~~~~
/usr/include/Random123/features/gccfeatures.h:39:102: fatal error: including_a_nonexistent_file_will_stop_some_compilers_from_continuing_with_a_hopeless_task: No such file or directory
 #include <including_a_nonexistent_file_will_stop_some_compilers_from_continuing_with_a_hopeless_task>
                                                                                                      ^
compilation terminated.

Expected results:
Successful compilation.

Additional info:
gccfeatures.h contains this:
#if !defined(__x86_64__) && !defined(__i386__) && !defined(__powerpc__)
#  error "This code has only been tested on x86 and powerpc platforms."
#include <including_a_nonexistent_file_will_stop_some_compilers_from_continuing_with_a_hopeless_task>
{ /* maybe an unbalanced brace will terminate the compilation */
 /* Feel free to try the Random123 library on other architectures by changing
 the conditions that reach this error, but you should consider it a
 porting exercise and expect to encounter bugs and deficiencies.
 Please let the authors know of any successes (or failures). */
#endif

Either this check should be disabled or the package should be archful and be built only for the supported arches.