On 2019/10/25 17:47, Rafael Sadowski wrote: > in Tue Oct 22, 2019 at 11:05:11AM +0100, Stuart Henderson wrote: > > Here are some of the ports persistently seeing this error from cmake/ninja: > > > > x11/kde-applications/audiocd-kio > > x11/kde-applications/kdeedu-data > > x11/kde-applications/kmbox > > x11/kde-applications/kshisen > > x11/lxqt/about > > x11/lxqt/obconf-qt > > x11/lxqt/runner > > > > Does anyone know when this started? Was it a bad cmake update sometime? > > I am hitting at least one of these every 2-3 bulk builds. > > > > This needs fixing some way or other, I am not going to reattempt builds for > > these in standard bulk builds any more so the packages and their dependents > > will just be missing. > > > > It is possible for you to go into the build directory and run > "ninja -d explain"? > Maybe the output can help me to find the issue.
I'll try to get that next time it happens. I can't keep all the failed build work directories from my bulks because I have failures, often in big ports, in nearly every bulk build (I do approx 20 per month).. > This is not a cmake issue, it's more a ninja issue. Of course you can > try: > > USE_NINJA = samurai > > That has always helped well so far! We can also fit it with: > > USE_NINJA = No I can't say if that actually fixes anything or not because reattempting the build with ninja will often fix it too. (But ports are supposed to build reliably). > If this not work, blame cmake! > > Sorry I can't help you much more. > > RS > It didn't used to happen (even with ninja), _something_ happened, and now it does. I'm just doing the builds. I'll try to help with information if I'm told what is needed but people committing to the ports involved in the breakage do need to take responsibility for tracking down and fixing them ..
