* On 2025-06-17 at 12:19 BST, Orgis, Dr. Thomas wrote:
Am 17.06.2025 um 11:52 schrieb Jonathan Perkin <jperkin%pkgsrc.org@localhost>: * On 2025-06-17 at 10:38 BST, Dr. Thomas Orgis wrote:Module Name: pkgsrc Committed By: thor Date: Tue Jun 17 09:38:01 UTC 2025 Modified Files: pkgsrc/math/suitesparse: Makefile Log Message: suitesparse: require fortran8 again, got downgraded by accident beforeNot sure what mk/ you are working from, but there is no such "fortran8" in the current pkgsrc mk/compiler infrastructure.Now I'm wholly confused. Ktnb wrote to me that the omission of fortran8 broke his build. I am not aware of doing the change to plain fortran intentionally, so reverted. My builds don't care either way. I just assumed fortran8 means Fortran 2008 language standard. If no such definition exists for pkgsrc, shouldn'd the build fail early?
Setting it to an unsupported value has the same effect as not setting it at all. pkglint would have warned you prior to commit:
WARN: Makefile:15: "fortran8" is not valid for USE_LANGUAGES. Use one of { ada c c++ c++03 c++0x c++11 c++14 c++17 c++20 c++23 c11 c17 c99 fortran fortran77 gnu++03 gnu++0x gnu++11 gnu++14 gnu++17
gnu++20 gnu++23 gnu11 gnu17 gnu99 objc objc-c++ } instead.
So you are effectively removing "fortran" from USE_LANGUAGES. If that
really fixes it (hard to tell as the package fails on illumos and macOS
daily bulk builds for different reasons) then that would be incredibly
strange, and I would strongly suspect the actual bug is something else
and would benefit from being looked into more thoroughly.
-- Jonathan Perkin pkgsrc.smartos.org Open Source Complete Cloud www.tritondatacenter.com