It would be great if the library build process included some kind of self testing to ensure it work. It would ensure broken architectures are discovered early. This is relevant on Debian where we build automatically on 20 architectures and it can take a while before anyone come around to test every one of the 50,000 binary packages in the archive on every architecture. In such setting it is best if the package test itself during build to notify the package maintainer early if there is a problem.
It would be best if 'make check' triggered such self test, as it is the way the automated tools will try to run a check automatically.
It would be great if the library build process included some kind of self testing to ensure it work. It would ensure broken architectures are discovered early. This is relevant on Debian where we build automatically on 20 architectures and it can take a while before anyone come around to test every one of the 50,000 binary packages in the archive on every architecture. In such setting it is best if the package test itself during build to notify the package maintainer early if there is a problem.
It would be best if 'make check' triggered such self test, as it is the way the automated tools will try to run a check automatically.