glibc run-built-tests option

Rajmohan. R Rajmohan.R@kpit.com
Wed Feb 26 11:12:53 GMT 2025


Hi All
Tried to run 'make check' in the standalone glibc-2.39 source code after compilation successful.

Compilation step successful.
L-16522:~/glibc-2.39/rajbld$ ../configure CC="gcc" --disable-sanity-checks
L-16522:~/glibc-2.39/rajbld$ make

Ran below command to verify whether only test binaries are created​, or test binaries + test are run.
L-16522:~/glibc-2.39/rajbld$ make check run-built-tests=no

Observed that, though the standalone is not a cross-compiled one, I commented the below lines and kept only run-built-tests=no in Makeconfig file.
Found that, still test binaries are run.
# Whether to run test programs built for the library's host system.
#ifndef run-built-tests
#ifeq (yes|,$(cross-compiling)|$(test-wrapper))
#run-built-tests = no
#else
#run-built-tests = yes
#endif
#endif
run-built-tests = no

Option 'run-built-tests' if set to 'no' shall not run test binaries is what the naming convention of the option says. But if set to 'no' for this options, still test binaries are created.

Could someone from team clarify why the above option is running test binaries despite options says it will not run binaries when given as option to 'make check'.

As the above option still runs the binaries , is this a bug. Please clarify

regards
rajmohan




More information about the Libc-help mailing list