liquid-dsp: don't leak impure builder cpu extensions into the build

By default the project builds with automatic vector extension detection
for the cpu. This leaks impure state into the executable and depending on
the builder results in executables that require AVX extensions.

Resolves #384082.
This commit is contained in:
Sergei Zimmerman
2025-02-22 21:49:33 +00:00
parent 9fb99dedbf
commit 9b45381683

View File

@@ -19,7 +19,16 @@ stdenv.mkDerivation rec {
sha256 = "sha256-3UKAwhYaYZ42+d+wiW/AB6x5TSOel8d++d3HeZqAg/8=";
};
configureFlags = lib.optionals stdenv.hostPlatform.isDarwin [ "LIBTOOL=${cctools}/bin/libtool" ];
configureFlags =
lib.optionals stdenv.hostPlatform.isDarwin [
"LIBTOOL=${cctools}/bin/libtool"
]
++ [
# Prevent native cpu arch from leaking into binaries. This might lead to
# poor performance, but having portable and working executables is more
# important.
(lib.enableFeature true "simdoverride")
];
nativeBuildInputs =
[ autoreconfHook ]