On 2017.10.16 09:05, Łukasz Wojniłowicz wrote: [snip...] > Commit 4ef19ac2ccfb6a3bb46598a22ecddcbe794a3e37 fixes your issue and > if not > then clean your installation or build tree. I did have an up-to-date pull, but you are correct, it appears my build tree was not clean. Starting from scratch, that error no longer appears.