bug#70982: test suite failures on OpenBSD

[Bruno Haible]

Hi Ileana,

Ileana Dumitrescu wrote:
> Tests 34 and 81 have been fixed [1] with these commits [2][3] in
> OpenBSD, and an additional test, 173, for using local versions of shared
> libraries is fixed by utilizing functionality added in this commit [4]. 
> The entire OpenBSD testsuite should be fixed in development now!
> 
> [1] https://github.com/gnu-libtool/ci-check/actions/runs/11726885546
> [2] 
> https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=7c310c9b0439a020add4c23d84ab33eeb486bd75
> [3] 
> https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=c7bfd6884ceae4e792b17c9ea89097e8d00dbe2b
> [4] 
> https://git.savannah.gnu.org/cgit/libtool.git/commit/?h=development&id=3996b1fddcaa543c8bf349314cac3ab4b07b4d1d

Thanks for working on this!

However, there are two things that I don't understand:

* Why two options, --test and --check, that do the same thing?
  In my understanding, "check" means doing a "test" with the a certain
  expectation, whereas "test" is unbiased.

* In which situations is the user expected to pass one of these options?
  - Is it only for libtool's own test suite?
  - Is it also for the test suite of a package (like GNU gettext)?
    If yes, does this mean that instead of executing a program through
      ../src/prog <some_arguments>
    the package's test suite needs to run
      ../libtool --mode=execute --test ../src/prog <some_arguments>  ?
    And what about interactive invocations of src/prog then?

Bruno