Has this issue been reported upstream? Or a PR sent to fix the issue?

I'm guessing this is caused by a change in meson in version 0.48
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

Reply via email to