Hi Bruno, Am Mi., 23. Juli 2025 um 09:33 Uhr schrieb Bruno Haible <br...@clisp.org>: > > Hi Marc, > > > the build-aux/run-test script recommends that the package is > > configured with "--disable-shared" "so that tests are real executables > > and not libtool wrapper scripts". > > Yep. If you compile with --enable-shared and then run valgrind > on the wrapper scripts, the logs would contain output about the > sh or bash process, which is not what the user wants. > > > I wonder why the script doesn't use the "libtool --mode execute > > valgrind ..." approach > > Because we don't know where 'libtool' is. It could be in "..", > or in "../..", or in "../../..", and so on. It depends on the > package's directory structure.
Thank you for the explanation. What about adding an option to run-test that tells it whether and where libtool is available? Of course, the user could just change the CHECKER argument but this would duplicate the logic whether the CHECKER argument is empty (not needing a libtool prefix) vs. the CHECKER argument is not. [...] Marc
