]> git.ipfire.org Git - thirdparty/binutils-gdb.git/commit
projects / thirdparty / binutils-gdb.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 8fc06b2) | patch
Don't build libctf tests in source dir
authorAlan Modra <amodra@gmail.com>
Fri, 17 Oct 2025 00:34:40 +0000 (11:04 +1030)
committerAlan Modra <amodra@gmail.com>
Fri, 17 Oct 2025 00:34:40 +0000 (11:04 +1030)
commit9c9106213ab41185b0475cab3670f4055cc5901d
treecc9ac6d285938b4d1ff6d5b8e63196af343881d2tree | snapshot
parent8fc06b252e8b1bc2fcab0cb4604f8406845fb2dacommit | diff
Don't build libctf tests in source dir

Running the libctf testsuite currently leaves big-struct-ctf.o in
libctf/testsuite/libctf-lookup/.

It ought to be possible to make the binutils source dir read-only,
and putting compiler output in the source dir leads to interesting
effects when testing multiple binutils targets in parallel.

* lib/ctf-lib.exp (run_lookup_test): For "link: objects" compile
objects in tmpdir.
libctf/testsuite/lib/ctf-lib.exp diff | blob | blame | history
A mirror of the official binutils-gdb repository