[libc] libc_execv_test_normal_exit and libc_execv_test_signal_exit never set compiler+linker flags

[nickdesaulniers]

IIUC, those two ninja targets are using add_executable/set_target_properties in libc/test/integration/src/unistd/CMakeLists.txt as part of unistd-integration-tests. execv_test.cpp and execve_test.cpp executes these binaries via corresponding execv/execve syscall.

Because they're not using existing test harnesess, it appears they don't set the compiler/linker flags correctly. This results in linkage failures when cross compiling.

[llvmbot]

@llvm/issue-subscribers-libc

Author: Nick Desaulniers (nickdesaulniers)

IIUC, those two ninja targets are using add_executable/set_target_properties in libc/test/integration/src/unistd/CMakeLists.txt as part of unistd-integration-tests. execv_test.cpp and execve_test.cpp executes these binaries via corresponding execv/execve syscall.

Because they're not using existing test harnesess, it appears they don't set the compiler/linker flags correctly. This results in linkage failures when cross compiling.