* Clang 16 testing: Found possible issues in configure! * Clang 16 testing: Please check /var/tmp/clang/dev-lang/python-3.12.0_p1/clang.diff * Final size of build directory: 163908 KiB (160.0 MiB) * Final size of installed tree: 188752 KiB (184.3 MiB) strip: llvm-strip --strip-unneeded -N __gentoo_check_ldflags__ -R .comment -R .GCC.command.line -R .note.gnu.gold-version /usr/bin/python3.12 /usr/lib/python3.12/lib-dynload/_asyncio.cpython-312-x86_64-linux-gnu.so ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_clang-20231125-175744 ------------------------------------------------------------------- The log matches a QA pattern or a pattern requested by a Gentoo developer.
Created attachment 875696 [details] emerge-info.txt
Created attachment 875697 [details] dev-lang:python-3.12.0_p1:20231125-222652.log.xz
Created attachment 875698 [details] emerge-history.txt
Created attachment 875699 [details] etc.clang.tar.xz
Created attachment 875700 [details] etc.portage.tar.xz
Created attachment 875701 [details] qlist-info.txt
Created attachment 875702 [details] var.tmp.clang.tar.xz
Thanks for the report! chflags(2)/lchflags(2) are FreeBSD-specific syscalls and function wrappers, no wonder it's not defined on a Linux system. I believe there is no issue here.
As it turns out, all python ebuilds already contain "QA_CONFIG_IMPL_DECL_SKIP=( chflags lchflags )" to explicitly mark this as a false positive since commit 3f5ab636b096ddc66b8ea093791fb9cdf62687ab (before this bugreport).
*** Bug 918602 has been marked as a duplicate of this bug. ***
(In reply to Gabi Falk from comment #9) > As it turns out, all python ebuilds already contain > "QA_CONFIG_IMPL_DECL_SKIP=( chflags lchflags )" to explicitly mark this as a > false positive since commit 3f5ab636b096ddc66b8ea093791fb9cdf62687ab (before > this bugreport). Thanks!
