Created attachment 647932 [details] emerge kde-frameworks/karchive-5.70.0-r1 build log Portage 2.3.99 (python 3.7.7-final-0, default/linux/arm64/17.0/desktop/plasma, gcc-9.3.0, glibc-2.30-r8, 4.14.0 aarch64) ================================================================= System Settings ================================================================= System uname: Linux-4.14.0-aarch64-with-gentoo-2.6 KiB Mem: 4039076 total, 3275960 free KiB Swap: 0 total, 0 free Timestamp of repository gentoo: Mon, 06 Jul 2020 09:30:01 +0000 Head commit of repository gentoo: 684ce5e609906f4954bf3ad218388dfb8b3f24f2 Head commit of repository genpi64: 7f94dfa1218e9960cf0aa3f4cead5aaec63a69c8 Head commit of repository sakaki-tools: 15cf8034d6396dd7345c004d3b5df14953c67a56 sh bash 5.0_p17 ld GNU ld (Gentoo 2.33.1 p2) 2.33.1 distcc 3.3.3 aarch64-unknown-linux-gnu [disabled] app-shells/bash: 5.0_p17::gentoo dev-lang/perl: 5.30.3::gentoo dev-lang/python: 2.7.18::gentoo, 3.7.7-r2::gentoo, 3.8.2-r2::gentoo dev-util/cmake: 3.16.5::gentoo sys-apps/baselayout: 2.6-r1::gentoo sys-apps/openrc: 0.42.1::gentoo sys-apps/sandbox: 2.18::gentoo sys-devel/autoconf: 2.13-r1::gentoo, 2.69-r4::gentoo sys-devel/automake: 1.16.1-r1::gentoo sys-devel/binutils: 2.33.1-r1::gentoo sys-devel/gcc: 9.3.0::gentoo sys-devel/gcc-config: 2.2.1::gentoo sys-devel/libtool: 2.4.6-r6::gentoo sys-devel/make: 4.2.1-r4::gentoo sys-kernel/linux-headers: 5.4-r1::gentoo (virtual/os-headers) sys-libs/glibc: 2.30-r8::gentoo Repositories: gentoo location: /usr/portage sync-type: rsync sync-uri: rsync://rsync.gentoo.org/gentoo-portage priority: -1000 sync-rsync-verify-metamanifest: yes sync-rsync-verify-max-age: 24 sync-rsync-extra-opts: sync-rsync-verify-jobs: 1 local location: /var/db/repos/local masters: gentoo crossdev location: /var/db/repos/crossdev masters: gentoo priority: 10 genpi64 location: /var/db/repos/genpi64 sync-type: git sync-uri: https://github.com/sakaki-/genpi64-overlay.git masters: gentoo priority: 20 sakaki-tools location: /var/db/repos/sakaki-tools sync-type: git sync-uri: https://github.com/sakaki-/sakaki-tools.git masters: gentoo priority: 50 ACCEPT_KEYWORDS="arm64" ACCEPT_LICENSE="*" CBUILD="aarch64-unknown-linux-gnu" CFLAGS="-O2 -pipe" CHOST="aarch64-unknown-linux-gnu" CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/sandbox.d /etc/terminfo" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" ENV_UNSET="DBUS_SESSION_BUS_ADDRESS DISPLAY GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR" FCFLAGS="-O2 -pipe" FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="-O2 -pipe" GENTOO_MIRRORS="http://distfiles.gentoo.org" LDFLAGS="-Wl,-O1 -Wl,--as-needed" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git" PORTAGE_TMPDIR="/var/tmp" USE="X a52 aac acl acpi activities alsa arm64 berkdb bluetooth branding bzip2 cairo cdda cdr cli crypt cups dbus declarative dri dts dvdr elogind emboss encode exif flac fortran gdbm gif gpm gtk iconv icu ipv6 jpeg kde kipi kwallet lcms ldap libnotify libtirpc mad mng mp3 mp4 mpeg ncurses nls nptl ogg opengl openmp pam pango pcre pdf phonon plasma png policykit ppds qml qt5 readline seccomp semantic-desktop spell split-usr ssl startup-notification svg tcpd tiff truetype udev udisks unicode upower usb vorbis widgets wxwidgets x264 xattr xcb xml xv xvid zlib" ADA_TARGET="gnat_2018" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_ARM="edsp thumb thumb2 v4 v5 v6 v7 v8 vfp vfp-d32 vfpv3 vfpv4" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 timing tsip tripmate tnt ublox ubx" INPUT_DEVICES="libinput" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LIBREOFFICE_EXTENSIONS="presenter-console presenter-minimizer" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php7-2" POSTGRES_TARGETS="postgres10 postgres11" PYTHON_SINGLE_TARGET="python3_7" PYTHON_TARGETS="python2_7 python3_7" RUBY_TARGETS="ruby25" USERLAND="GNU" VIDEO_CARDS="fbdev dummy v4l" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CC, CPPFLAGS, CTARGET, CXX, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL, LINGUAS, MAKEOPTS, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
This error is almost always called by a broken system clock. Please verify your date and time is correct.
(In reply to Sam James (sec padawan) from comment #1) > This error is almost always called by a broken system clock. Please verify > your date and time is correct. Hi Sam James, I check the system date and assure it is correct. Could you investigate the build log more and give me some advice? I tried sync clock with the server (by ntpdate pool.ntp.org) and re-emerge many times, but the problem still persists. Thanks in advance.
You should really fix your system, this is just the same as bug 729676. *** This bug has been marked as a duplicate of bug 729676 ***
(In reply to Andreas Sturmlechner from comment #3) > You should really fix your system, this is just the same as bug 729676. > > *** This bug has been marked as a duplicate of bug 729676 *** I corrected the system clock already but the emerge was always failed because the ninja build was failed. Already tried to re-emerging many times but it was still failed.
Do not reopen this bug again. This is a warning. *** This bug has been marked as a duplicate of bug 729676 ***
Re-opening per bug 729676 comment 12, since the problem is no longer reproducible with elogind.
Please upgrade to the latest ninja release (0.10.0). If that does not resolve the issue, I don't think we can help you much; this seems that this is a problem isolated to your system. If you can troubleshoot and diagnose the problem further, we would be happy to help you write a patch or backport any necessary fixes from upstream.
(In reply to Mike Gilbert from comment #7) > Please upgrade to the latest ninja release (0.10.0). > > If that does not resolve the issue, I don't think we can help you much; this > seems that this is a problem isolated to your system. > > If you can troubleshoot and diagnose the problem further, we would be happy > to help you write a patch or backport any necessary fixes from upstream. My system have latest version of ninja (1.9.0) installed. Can I emerge the older version of ninja?
That's not correct: $ eshowkw dev-util/ninja Keywords for dev-util/ninja: | | u | | a a p s a r | n | | m r h p p s l i i m m | e u s | r | d a m p p c a x 3 p a s 6 i | a s l | e | 6 r 6 p p 6 r 8 9 h 6 c 8 p | p e o | p | 4 m 4 a c 4 c 6 0 a 4 v k s | i d t | o -------------+-----------------------------+-------+------- 1.8.2 | + + + + + + + + + ~ ~ o ~ ~ | 6 # 0 | gentoo 1.8.2-r1 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ | 6 # | gentoo 1.8.2-r2 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ | 6 # | gentoo 1.9.0 | + + + + + + + + + ~ ~ ~ ~ ~ | 7 o | gentoo [I]1.10.0 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ | 7 o | gentoo 9999 | o o o o o o o o o o o o o o | 7 o | gentoo
(In reply to Andreas Sturmlechner from comment #9) > That's not correct: > > $ eshowkw dev-util/ninja > Keywords for dev-util/ninja: > | | u | > | a a p s a r | n | > | m r h p p s l i i m m | e u s | r > | d a m p p c a x 3 p a s 6 i | a s l | e > | 6 r 6 p p 6 r 8 9 h 6 c 8 p | p e o | p > | 4 m 4 a c 4 c 6 0 a 4 v k s | i d t | o > -------------+-----------------------------+-------+------- > 1.8.2 | + + + + + + + + + ~ ~ o ~ ~ | 6 # 0 | gentoo > 1.8.2-r1 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ | 6 # | gentoo > 1.8.2-r2 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ o ~ ~ | 6 # | gentoo > 1.9.0 | + + + + + + + + + ~ ~ ~ ~ ~ | 7 o | gentoo > [I]1.10.0 | ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ | 7 o | gentoo > 9999 | o o o o o o o o o o o o o o | 7 o | gentoo I have another question, do not know if it relates to ninja or not. When emerging some packages use ninja to build, I saw that it usually causes system clock broken, i.e the sytem time will be set to the future. Can you tell me in which condition does the ninja break the system clock?
(In reply to Mike Gilbert from comment #7) > Please upgrade to the latest ninja release (0.10.0). > > If that does not resolve the issue, I don't think we can help you much; this > seems that this is a problem isolated to your system. > > If you can troubleshoot and diagnose the problem further, we would be happy > to help you write a patch or backport any necessary fixes from upstream. It is very amazing that I can emerge archive successfully after re-emerging the ninja package. But some the issue is keep going on for other packages.
(In reply to Mike Gilbert from comment #7) > Please upgrade to the latest ninja release (0.10.0). > > If that does not resolve the issue, I don't think we can help you much; this > seems that this is a problem isolated to your system. > > If you can troubleshoot and diagnose the problem further, we would be happy > to help you write a patch or backport any necessary fixes from upstream. I have tried to emerge a lot of packages and by my experience, the system's clock was usually broken whenever the package was compiled with ninja. I searched for google about ninja's dirty build problem and saw a lot of people faced the same issue, they also complained about ninja as a buggy program.
You have buggy hardware.
(In reply to Andreas Sturmlechner from comment #13) > You have buggy hardware. In fact, I used qemu to build arm64 gentoo system qemu-system-aarch64 -M virt \ -cpu cortex-a72 \ -smp 8 \ -m 8192 \ -kernel ./linux/vmlinux-4.14.0-arm64 \ -initrd ./initrd/initrd-4.14.0-arm64.img \ -nographic \ -serial mon:stdio \ -append "rw root=/dev/vda3 rootfstype=ext4 fsck.repair=yes net.ifnames=0 rootwait memtest=1" \ -drive file=./pigen64.img,format=raw,if=sd,id=hd-root \ -device virtio-blk-device,drive=hd-root \ -netdev user,id=net0,net=192.168.1.1/24,dhcpstart=192.168.1.235,hostfwd=tcp::5566-:22 \ -device virtio-net-device,netdev=net0 \ -no-reboot
*** This bug has been marked as a duplicate of bug 729676 ***
