It's a bug that has since been fixed by kernel commit
2220fc1ab363e6fab1f321430d69be17a8b92bd7 ("uapi: add missing install
of dma-buf.h"). The header was originally added in 4.10, and the fix
commit is in 4.11-rc1.
I guess we just need to hack around it in sys-kernel/linux-headers-4.10.
On Wed, Mar 29, 2017 at 12:34 PM, Paweł Hajdan, Jr.
wrote:
> I was packaging chromium-59.0.3053.3 . I worked around the problem
> described here, but I'd like to find the right long term solution.
>
> I was hitting the following compile error:
>
> ../../ui/gfx/linux/client_native_pixmap_dmabuf.cc:
I was packaging chromium-59.0.3053.3 . I worked around the problem
described here, but I'd like to find the right long term solution.
I was hitting the following compile error:
../../ui/gfx/linux/client_native_pixmap_dmabuf.cc:39:27: fatal error:
linux/dma-buf.h: No such file or directory
#inclu
