From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C8822139694 for ; Wed, 29 Mar 2017 17:15:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F2C1D1421E; Wed, 29 Mar 2017 17:15:11 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id A40A0141EA for ; Wed, 29 Mar 2017 17:15:11 +0000 (UTC) Received: from mail-io0-f180.google.com (mail-io0-f180.google.com [209.85.223.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: floppym) by smtp.gentoo.org (Postfix) with ESMTPSA id 860AF3413B7 for ; Wed, 29 Mar 2017 17:15:10 +0000 (UTC) Received: by mail-io0-f180.google.com with SMTP id l7so3205793ioe.3 for ; Wed, 29 Mar 2017 10:15:10 -0700 (PDT) X-Gm-Message-State: AFeK/H1+kMySbc5jnHEFuILbdUkg79898XchmjiEVQFuxCuiLusJhXByPARhj6+vYuElMlr0/jK5oTiUHYJ+9g== X-Received: by 10.107.1.16 with SMTP id 16mr2115005iob.44.1490807708488; Wed, 29 Mar 2017 10:15:08 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.107.39.136 with HTTP; Wed, 29 Mar 2017 10:14:48 -0700 (PDT) In-Reply-To: <8ade455f-0287-a30a-8765-5261a9a5f6ae@gentoo.org> References: <8ade455f-0287-a30a-8765-5261a9a5f6ae@gentoo.org> From: Mike Gilbert Date: Wed, 29 Mar 2017 13:14:48 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [gentoo-dev] linux/dma-buf.h mysteriously missing To: Gentoo Dev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 5df6c216-3c10-437c-bcab-a8ffdb4f5408 X-Archives-Hash: 35661c92825dd227c52fbbc4782d629f On Wed, Mar 29, 2017 at 12:34 PM, Pawe=C5=82 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:39:27: fatal error: > linux/dma-buf.h: No such file or directory > #include > > Despite having sys-kernel/linux-headers-4.10 installed, I do not have > that header. Interestingly, it is present in the tarball > (gentoo-headers-base-4.10.tar.xz), but doesn't seem to get installed. > > This is the workaround I applied: > > > This is part of the chromium code in question: > > > > #if LINUX_VERSION_CODE < KERNEL_VERSION(4, 6, 0) > #include > > struct local_dma_buf_sync { > __u64 flags; > }; > > #define LOCAL_DMA_BUF_SYNC_READ (1 << 0) > #define LOCAL_DMA_BUF_SYNC_WRITE (2 << 0) > #define LOCAL_DMA_BUF_SYNC_RW \ > (LOCAL_DMA_BUF_SYNC_READ | LOCAL_DMA_BUF_SYNC_WRITE) > #define LOCAL_DMA_BUF_SYNC_START (0 << 2) > #define LOCAL_DMA_BUF_SYNC_END (1 << 2) > > #define LOCAL_DMA_BUF_BASE 'b' > #define LOCAL_DMA_BUF_IOCTL_SYNC \ > _IOW(LOCAL_DMA_BUF_BASE, 0, struct local_dma_buf_sync) > > #else > #include > #endif It seems the file was not added to include/uapi/linux/Kbuild. This was likely an oversight by the kernel developer who added the header file. I would suggest filing a bug.