All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99972] xf86drm.h:40:17: error: drm.h: No such file or directory
Date: Sun, 26 Feb 2017 13:36:10 +0000	[thread overview]
Message-ID: <bug-99972-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 960 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99972

            Bug ID: 99972
           Summary: xf86drm.h:40:17: error: drm.h: No such file or
                    directory
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: libdrm
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: joqmos@gmail.com

In libdrm-2.4.75, xf86drm.h and xf86drmMode.h include drm.h, which doesn't
exist.
drm.h and friends are installed in /usr/local/include/libdrm.

When compiling a C program that includes xf86dri.h with GCC, the following
error message appears:

  /usr/include/xf86drm.h:40:17: fatal error: drm.h: No such file or directory
   #include <drm.h>
                   ^

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2249 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-02-26 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26 13:36 bugzilla-daemon [this message]
2017-02-26 13:51 ` [Bug 99972] xf86drm.h:40:17: error: drm.h: No such file or directory bugzilla-daemon
2017-02-26 14:22 ` bugzilla-daemon
2017-02-26 14:39 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-99972-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.