There's a merged pull request on the void-packages repository sympow: on musl, do not mess with fpu control word https://github.com/void-linux/void-packages/pull/34209 Description: It turns out doing that results in broken precision, and not doing it fixes it. A simple way to test it is to run $ sympow -curve '[0,0,0,0,1]' -analrank ... Analytic Rank is 0 : L-value 7.01091e-01 When broken this prints "7.01092e-01" instead. The actual value computed to 128 bits with pari is: $ echo 'elllseries(ellinit([0,0,0,0,1]),1)' | gp -q 0.70109105266272713058750953952514706773 so the glibc output is the correct one. It seems to me that what is broken is not computing but printing, but this is important since sagemath parses sympow output. This affects sagemath doctests as in $ sage -t src/sage/lfunctions/sympow.py ... (3 failures) After this commit, the doctest in question passes. #### Testing the changes - I tested the changes in this PR: **YES** The corresponding doctest in sagemath passes on musl with this change; it was failing before.