On Fri, 22 Mar 2024 20:11:57 -0400 Jack <ostrof...@users.sourceforge.net> wrote:
> It seems the problem is that the enviroment file in the temp dir of > the build area is sourced when you run ebuild/emerge. (It's among > the first output when you run ebuild.) Since that file was created > based on the state of the ebuild when the first emerge/ebuild was > run, editing the ebuild file doesn't affect it. I ended up finding a > place to unset CHECKREQS_FAILED, and the compile is now continuing. According to check-reqs.eclass, you can also bypass the check by exporting CHECKREQS_DONOTHING=1. I assume this would work for a resumed build too. Cheers, Bryan
