AC_FUNC_ALLOCA AC_FUNC_GETLOADAVG FAIL: AC_FUNC_GETLOADAVG, problem with executing AC_FUNC_UTIME_NULL AC_FUNC_STRCOLL AC_FUNC_SETVBUF_REVERSED ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-hardened_test_20190209-222026 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Rust versions: [1] rust-1.32.0 * emerge -qpvO sys-devel/autoconf [ebuild R ] sys-devel/autoconf-2.69-r4 USE="-emacs"
Created attachment 565188 [details] emerge-info.txt
Created attachment 565190 [details] emerge-history.txt
Created attachment 565192 [details] environment
Created attachment 565194 [details] etc.portage.tbz2
Created attachment 565196 [details] logs.tbz2
Created attachment 565198 [details] sys-devel:autoconf-2.13-r1:20190213-190826.log
Created attachment 565200 [details] temp.tbz2
Update summary. [something] is used when something refers to an overlay
lto_tinderbox has reproduced this issue with version 2.13-r6 - Updating summary.
*** Bug 882439 has been marked as a duplicate of this bug. ***
From /var/tmp/portage/sys-devel/autoconf-2.13-r7/work/autoconf-2.13/testsuite/autoconf.log: ``` AC_FUNC_GETLOADAVG /var/tmp/portage/sys-devel/autoconf-2.13-r7/work/autoconf-2.13/autoconf -m /var/tmp/portage/sys-devel/autoconf-2.13-r7/work/autoconf-2.13 AC_FUNC_GETLOADAVG.in > AC_FUNC_GETLOADAVG FAIL: AC_FUNC_GETLOADAVG, problem with executing ls: cannot access '/dev/kmem': No such file or directory ```
(In reply to Sam James from comment #11) > ls: cannot access '/dev/kmem': No such file or directory > ``` Indeed, this is a bubblewrap environment, /dev only contains: 17-1-desktop-plasma-j4-20221120-222342 /var/tmp/tb # ls -l /dev/ total 0 crw--w---- 1 root tty 136, 0 Nov 22 09:03 console lrwxrwxrwx 1 root root 11 Nov 22 09:03 core -> /proc/kcore lrwxrwxrwx 1 root root 13 Nov 22 09:03 fd -> /proc/self/fd crw-rw-rw- 1 root root 1, 7 Nov 16 20:16 full drwxrwxrwt 2 root root 40 Nov 22 09:03 mqueue crw-rw-rw- 1 root root 1, 3 Nov 16 20:16 null lrwxrwxrwx 1 root root 8 Nov 22 09:03 ptmx -> pts/ptmx drwxr-xr-x 2 root root 0 Nov 22 09:03 pts crw-rw-rw- 1 root root 1, 8 Nov 16 20:16 random drwxrwxrwt 2 root root 40 Nov 22 09:03 shm lrwxrwxrwx 1 root root 15 Nov 22 09:03 stderr -> /proc/self/fd/2 lrwxrwxrwx 1 root root 15 Nov 22 09:03 stdin -> /proc/self/fd/0 lrwxrwxrwx 1 root root 15 Nov 22 09:03 stdout -> /proc/self/fd/1 crw-rw-rw- 1 root tty 5, 0 Nov 20 16:49 tty crw-rw-rw- 1 root root 1, 9 Nov 16 20:16 urandom crw-rw-rw- 1 root root 1, 5 Nov 16 20:16 zero
but even outside I do not have that device here.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d7dbfacbf92767bfa5aa46c9cc7ee12dcbcc558f commit d7dbfacbf92767bfa5aa46c9cc7ee12dcbcc558f Author: Sam James <sam@gentoo.org> AuthorDate: 2024-01-22 11:50:12 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-01-22 11:50:12 +0000 dev-build/autoconf: skip AC_FUNC_GETLOADAVG test for 2.13 The macro itself is broken in autoconf-2.13 but this is caused by newer kernels etc rather than anything else. Very, very few packages use autoconf-2.13, let alone AC_FUNC_GETLOADAVG, so not going to worry about it much. Do as Fedora and Debian do and skip the test for it. Closes: https://bugs.gentoo.org/406723 Closes: https://bugs.gentoo.org/677926 Signed-off-by: Sam James <sam@gentoo.org> dev-build/autoconf/autoconf-2.13-r8.ebuild | 1 + .../autoconf-2.13-skip-AC_FUNC_GETLOADAVG-test.patch | 20 ++++++++++++++++++++ 2 files changed, 21 insertions(+)
