All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 74712] New: libkms not enabled on DragonFly
Date: Sat, 08 Feb 2014 13:55:22 +0000	[thread overview]
Message-ID: <bug-74712-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 74712
          Assignee: dri-devel@lists.freedesktop.org
           Summary: libkms not enabled on DragonFly
          Severity: normal
    Classification: Unclassified
                OS: BSD (Others)
          Reporter: ftigeot@wolfpond.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: XOrg CVS
         Component: libdrm
           Product: DRI

Created attachment 93657
  --> https://bugs.freedesktop.org/attachment.cgi?id=93657&action=edit
Enable libkms on DragonFly

On DragonFly systems, libdrm's configure script does not enable libkms support.

Running ./autogen.sh without any parameter gives this result:

  libdrm 2.4.52 will be compiled with:

    libkms         no


The attached patch fixes the relevant check in configure.ac

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

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

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

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

             reply	other threads:[~2014-02-08 13:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 13:55 bugzilla-daemon [this message]
2014-03-03  7:30 ` [Bug 74712] libkms not enabled on DragonFly 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-74712-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.