We could mark it as MAKE_JOBS_UNSAFE for the moment -- feel free to do so :)
On 9 February 2018 at 23:27, Adriaan de Groot <adri...@bionicmutton.org>
> On Friday, 9 February 2018 20:56:18 CET Tobias C. Berner wrote:
> > this is a timing issue in the build (something does not get properly
> > ordered). You can try building it without any parallel makejobs -- which
> > might make it succeed.
> > I'm lucky enough that it does not trigger it often for me. -- i.e. try
> > again, it could work.
> I haven't seen it at all - I think my pou is limited to 6 jobs.
> > Upstream is aware of the issue already.
> Aware, yes, but unlikely to spend time hunting down the missing arc in the
> dependency graph. I'll have to sit down at some point and check most
> what is going on. (Possibly making the JSON generation much much slower
> show it up, too) (Maybe using gmake instead of ninja will solve it, too)