Closed aont closed 2 months ago
From the NO_AVX2=1 in your build log, it looks as if the c_check script has somehow decided that your (cross-)compiler is too old to support AVX2. (That version check is supposed to trigger for gcc versions earlier than 4.6). Can you please post the output of x86_64-w64-mingw32-gcc-posix -dumpversion
? (You should get it to build by changing lines 363,364 of c_check from no_avx2=1
, oldgcc=1
to no_avx2=0
and oldgcc=0
)
@martin-frbg Thanks for the quick reply.
$ x86_64-w64-mingw32-gcc-posix -dumpversion
13-posix
$ x86_64-w64-mingw32-gcc-win32 -dumpversion
13-win32
I forgot to write OpenBLAS version. I used v0.3.27.
By changing lines of c_check
(though the line number is different), binary is built and dgemm.goto runs without error!
I also confirmed with 886acfc .
Thanks, somewhat unfair that whoever packaged that mingw-gcc would use this non-numeric format (and somewhat naive of my script to expect it to be either a single number or a dotted "major.minor version).
Issue
I wanted to build a binary for Windows Haswell.
As a cross build host, I used
Ubuntu 24.04 LTS
withgcc-mingw-w64-x86-64-posix
andgcc-mingw-w64-x86-64-posix
installed .The build command I used is
make CC=x86_64-w64-mingw32-gcc-posix HOSTCC=gcc TARGET=HASWELL FC=x86_64-w64-mingw32-gfortran-posix CROSS=1 libs netlib
One of the error messages is
The entire build log is attached. openblas_make_log.txt
Same issue occurs with
gcc-mingw-w64-x86-64-win32
.If TARGET=SANDYBRIDGE or TARGET=SKYLAKEX is specified, binary is build without error and I found dgemm.goto runs without error.
Environment
build machine's CPU: INTEL(R) XEON(R) PLATINUM 8562Y+