Build fails when using a specific architecture about fuzzuf

[retrage]

I tried building fuzzuf on the exactly same CPU model with containerized build. It successfully built and passed tests. I think this issue is due to the apt package rather than fuzzuf itself.

[key-moon]

It works in my environment too. But when I tried to compile a random file in the docker environment with the -march=tigerlake option, it failed. I think why containerized build succeeded is due to the fact that the -march option is only set in the release configuration, and the default configuration is set to the build.

fuzzuf/CMakeLists.txt

Lines 185 to 188 in 0412d20

	set(CMAKE_CXX_FLAGS_DEBUG "-g ${ADDITIONAL_WARNING_FLAGS_STR}")
	set(CMAKE_C_FLAGS_DEBUG "-g ${ADDITIONAL_WARNING_FLAGS_STR}")
	set(CMAKE_CXX_FLAGS_RELEASE "-march=native -O3 ${ADDITIONAL_WARNING_FLAGS_STR}")
	set(CMAKE_C_FLAGS_RELEASE "-march=native -O3 ${ADDITIONAL_WARNING_FLAGS_STR}")

Unsurprisingly, when I try to build with the release configuration like ./scripts/dev_cli.sh build --release, the same problem happened.