Assume cross-compilation if host and target os differ

fixes 1674

clang 3.4 managed to accept the original test code, only to fail on the actual Skylake asm later

With this change, OpenBLAS builds and all tests pass on OpenBSD 6.2
using Clang. Tested on x86-64 only, with and without DYNAMIC_ARCH=1.

Conflicts:
	CONTRIBUTORS.md

Fixes build with TDM-GCC

Signed-off-by: Shivraj Patil <shivraj.patil@imgtec.com>

Signed-off-by: Shivraj Patil <shivraj.patil@imgtec.com>

Signed-off-by: Shivraj Patil <shivraj.patil@imgtec.com>

Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>

MIPS P5600(32 bit) and I6400(64 bit) cores support added.

Seperated mips and mips64 files.
Configurations support for mips 32 bit.

Signed-off-by: Shivraj Patil <shivraj.patil@imgtec.com>

This is necessary to avoid the false detection of a cross-compiling
environment.

If the path involves `-`, this would have otherwise detected this as a cross compile suffix.

e.g.
make HOSTCC=gcc CC=arm-linux-androideabi-gcc NO_LAPACK=1 TARGET=ARMV7

In Android NDK, it uses armeabi-v7a-hard ABI.
TARGET_CFLAGS += -mhard-float -D_NDK_MATH_NO_SOFTFP=1
TARGET_LDFLAGS += -Wl,--no-warn-mismatch -lm_hard
For more information, please check hard-float example at
android_ndk/tests/device/hard-float/jni/.

This is necessary to avoid the false detection of a cross-compiling environment.

`uname -m` returns "amd64" on some systems.

Signed-off-by: Timothy Gu <timothygu99@gmail.com>

For LAPACKE, use LAPACK_COMPLEX_STRUCTURE.
The reson is lsbcc didn't define complex I in complex.h.