Compiled shared object is not portable across kernel versions about crypt-argon2

[Leont]

Yeah, by default it compiles with native optimizations, but when packaging that may not be appropriate because target systems may lack instruction sets that the build system does have (e.g. AVX2/AVX512). Debian patches this logic out, it sounds like you want to do the same.

[level420]

@Leont I've been also struggling when creating a docker image based on the official perl 5.38 debian bookworm image, where I've simply added cpanm Crypt::Argon2 to the Dockerfile. Then I've tested everything thoroughly on several development and staging servers, just to find out that it doesn't work on our production servers.

Would It be possible to have some env variable which could be set to disable the -march-native flag?

[level420]

Just found commit 356eaa4 where this is already implemented via environment variable CRYPT_ARGON2_ARCH.

I think it would be helpful for others if this is documented and found via e.g. metacpan.org

[Leont]

I think it would be helpful for others if this is documented and found via e.g. metacpan.org

That is a very reasonable point.

[Leont]

I have just release a trial version that implements runtime implementation switching. Testing (e.g. cpanm LEONT/Crypt-Argon2-0.024-TRIAL.tar.gz) in a wide variety of environments would be much appreciated.

[level420]

@Leont does this mean that when now installing via cpanm LEONT/Crypt-Argon2-0.023-TRIAL.tar.gz the default is not to set the -arch compiler flag?

[Leont]

@Leont does this mean that when now installing via cpanm LEONT/Crypt-Argon2-0.023-TRIAL.tar.gz the default is not to set the -arch compiler flag?

It compiles versions with and without arch, and at runtime checks which ones are supported on that CPU :-)