libamplsolver: fix build on non-trapping FP architectures

[qbisi]

This code snippet will fail to compile on loongarch64 (see https://github.com/ampl/asl/blob/master/src/solvers/fpinit.c#L1437-L148)

#if defined(_FPU_IEEE) && defined(_FPU_EXTENDED) && defined(_FPU_DOUBLE)
	__fpu_control = _FPU_IEEE - _FPU_EXTENDED + _FPU_DOUBLE;
	_FPU_SETCW(__fpu_control);
#elif defined(__i386__) || defined(__x86_64__)
	__fpu_control = 0x27f;
	_FPU_SETCW(__fpu_control);
#elif defined(FE_ALL_EXCEPT)
	fedisableexcept(FE_ALL_EXCEPT);
#else
	!!!! How does this system work?
	!!!! Either figure it out (and modify this text),
	!!!! or compile fpinit.c with -DNO_fpu_control .

cause having macro FE_ALL_EXCEPT does not mean we have func fedisableexcept

according to chatgpt

架构	FE_ALL_EXCEPT	fedisableexcept()
x86_64	✔	✔
i386	✔	✔
aarch64	✔	✔
armv7	✔	✔
riscv64	✔	✘
loongarch64	✔	✘
musl (any)	✔	✘

cc @wegank should we do the same for riscv and musl? i can only valid this pr on loongarch64.

Things done

• Built on platform:
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• Tested, as applicable:
  • NixOS tests in nixos/tests.
  • Package tests at passthru.tests.
  • Tests in lib/tests or pkgs/test for functions and "core" functionality.
• Ran nixpkgs-review on this PR. See nixpkgs-review usage.
• Tested basic functionality of all binary files, usually in ./result/bin/.
• Nixpkgs Release Notes
  • Package update: when the change is major or breaking.
• NixOS Release Notes
  • Module addition: when adding a new NixOS module.
  • Module update: when the change is significant.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

---

Add a 👍 reaction to pull requests you find important.

[wegank]

For riscv64-linux, sure, I've checked that libamplsolver fails to build there without -DNO_fpu_control.

For Musl on exotic platforms (apparently, x86_64-linux and aarch64-linux do not need the flag), I would say it's not worth the effort...