When sys-devel/gdb is compiled without the python USE flag, libcxx will fail a single test libcxx/gdb/gdb_pretty_printer_test.sh.cpp since it seems to rely on a gdb_pretty_printer_test.sh.cpp.py file to run. Compiling gdb with the python USE flag enabled fixes the problem. If the test flag is enabled, we should probably add sys-devel/gdb[python] to the ebuild for ridiculous people like me who try to run minimal setups, lol :) Reproducible: Always Steps to Reproduce: 1. compile gdb -python 2. compile and test libcxx 3. profit Actual Results: libcxx fails the test phase Expected Results: this should be expected since gdb was compiled without python support and libcxx requires it for testing
Created attachment 764159 [details] failure build log
Created attachment 764160 [details] success! build log
Thanks for the report, attaching *both* logs (really helpful, thank you!), diagnosing the issue!
Oh, nit: if only attaching one file, can compress without using tar.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6d677f6922e0ac2433cf3d0189004e8b9b1fb211 commit 6d677f6922e0ac2433cf3d0189004e8b9b1fb211 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-02-02 07:20:29 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-02-02 07:20:29 +0000 sys-libs/libcxx: depend on sys-devel/gdb[python] for tests Closes: https://bugs.gentoo.org/832524 Signed-off-by: Sam James <sam@gentoo.org> sys-libs/libcxx/libcxx-13.0.1.9999.ebuild | 1 + sys-libs/libcxx/libcxx-13.0.1_rc3.ebuild | 1 + sys-libs/libcxx/libcxx-14.0.0.9999.ebuild | 1 + 3 files changed, 3 insertions(+)
