Created attachment 816130 [details] build.log System time is accurate to the second.
Created attachment 816133 [details] qlop -d 2022-10-01 -d 2022-10-03
Created attachment 816136 [details] emerge --info
What file system is /var/tmp/portage on? What mount options? Does it work if you delete the contents first?
(In reply to Sam James from comment #3) > What file system is /var/tmp/portage on? What mount options? Does it work if > you delete the contents first? # mount | grep /dev/sda2 /dev/sda2 on / type jfs (rw,relatime,sync) Do you think that relatime option is giving me issues? I can't seem to unset it. I tried: mount -o remount,rw,sync / Removal of files in /var/tmp/portage does not matter.
relatime should be OK, but I admit I don't remember the last time I saw someone using JFS ;) Maybe worth a go without it? Wonder if you mount a tmpfs, if that works?
(Sorry, ignore "give a go without it")
(In reply to Sam James from comment #5) > relatime should be OK, but I admit I don't remember the last time I saw > someone using JFS ;) > > Maybe worth a go without it? Wonder if you mount a tmpfs, if that works? I tried that: # mount | grep portage tmpfs on /var/tmp/portage type tmpfs (rw,nosuid,nodev,noatime,size=4194304k,mode=775,uid=250,gid=250,inode64) But no dice, same error :-(. Seems to be a semi-common thing with Ninja..
Huh. Okay. 1. Can you build older versions of opencolorio? 2. Does anything else using CMake and/or Meson work? 3. I know this sounds like a reach, but try rebuilding ninja?
(In reply to Sam James from comment #5) > relatime should be OK, but I admit I don't remember the last time I saw > someone using JFS ;) Aah yes, JFS is my trusty workhorse in the last ~20ish years. I trust it blindly, fastest, lowest resources, optionally case-insensitive (not in this case). It's my go-to fs. Do need to re-benchmark some time, last time I checked must be around ~2010's or something.
(In reply to Sam James from comment #8) > Huh. Okay. > > 1. Can you build older versions of opencolorio? > 2. Does anything else using CMake and/or Meson work? > 3. I know this sounds like a reach, but try rebuilding ninja? 1. Tested with current stable 2.1.1-r7, same issue 2. Yes, am in process of building ~975 packages, many CMake and Meson things passing by 3. Tried that, but didn't work (still get the 100 retries)
Unbelievable but true, I had to reboot. After reboot this issue went away. Note that there are no other config changes.
(In reply to Rubin Simons from comment #11) > Unbelievable but true, I had to reboot. After reboot this issue went away. > Note that there are no other config changes. Huh!
