Created attachment 342910 [details]
Failure from one of the affected ebuilds
I was rebuilding world with --jobs on Solaris when several builds failed because of an IOError. Oracle's documentation says:
Perhaps a process called fcntl(2) with the F_SETLK or F_SETLKW option, and the system maximum was exceeded. The system contains several different locking subsystems, including fcntl(2), the NFS lock daemon, and mail locking. All subsystems can produce this error.
EPREFIX was on NFS while PORTAGE_TMPDIR was on UFS.
Handle ENOLCK with loop:
Prefix portage with fix committed
This is fixed in 18.104.22.168 and 2.2.0_alpha170.