All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 52549] New: libdrm 2.4.37 compilation fails if ETIME not defined
Date: Thu, 26 Jul 2012 14:49:58 +0000	[thread overview]
Message-ID: <bug-52549-502@http.bugs.freedesktop.org/> (raw)

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

             Bug #: 52549
           Summary: libdrm 2.4.37 compilation fails if ETIME not defined
    Classification: Unclassified
           Product: DRI
           Version: XOrg CVS
          Platform: All
        OS/Version: BSD (Others)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: libdrm
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: davshao@gmail.com


For operating systems such as DragonFly BSD, ETIME may not be defined, let
alone POSIX STREAMS implemented.  libdrm 2.4.37 in current pkgsrc failed to
compile on DragonFly BSD 3.1-DEVEL i386 and x86_64 until a patch was added to
define ETIME if it was not already defined:

ETIME is not defined on DragonFly BSD, work around it.

--- intel/intel_bufmgr_gem.c.orig       2012-07-02 15:22:14.326942000 +0000
+++ intel/intel_bufmgr_gem.c
@@ -54,6 +54,9 @@
 #include <stdbool.h>

 #include "errno.h"
+#ifndef ETIME
+#define ETIME ETIMEDOUT
+#endif
 #include "libdrm_lists.h"
 #include "intel_bufmgr.h"
 #include "intel_bufmgr_priv.h"

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2012-07-26 14:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 14:49 bugzilla-daemon [this message]
2012-08-01  4:48 ` [Bug 52549] libdrm 2.4.37 compilation fails if ETIME not defined bugzilla-daemon
2012-10-06  8:12 ` bugzilla-daemon
2013-03-03  8:51 ` 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-52549-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.