public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonyoung Shim <jy0922.shim@samsung.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: Alex Deucher <Alexander.Deucher@amd.com>,
	ML dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] xf86drm: fix build error by udev dependency
Date: Mon, 01 Jun 2015 11:52:31 +0900	[thread overview]
Message-ID: <556BC8EF.2000403@samsung.com> (raw)
In-Reply-To: <CACvgo51XccaQi0u9qiVpPVws2YG__zTTwjzjFcLhAEwuLrUDUA@mail.gmail.com>

On 05/30/2015 10:02 PM, Emil Velikov wrote:
> On 29 May 2015 at 07:34, Joonyoung Shim <jy0922.shim@samsung.com> wrote:
>> On 05/28/2015 10:02 PM, Emil Velikov wrote:
>>> On 28 May 2015 at 00:56, Joonyoung Shim <jy0922.shim@samsung.com> wrote:
>>>> The build error is introduced by commit fde496917682 ("Add device
>>>> enumeration interface (v4)") if don't enable udev. Can solve as check
>>>> UDEV dependency.
>>>>
>>>>   CC       libdrm_la-xf86drm.lo
>>>> xf86drm.c:66:21: fatal error: libudev.h: No such file or directory
>>>>  #include "libudev.h"
>>>>                      ^
>>>> compilation terminated.
>>>> make[2]: *** [libdrm_la-xf86drm.lo] Error 1
>>>>
>>>> Signed-off-by: Joonyoung Shim <jy0922.shim@samsung.com>
>>>> ---
>>>>  xf86drm.c | 4 ++++
>>>>  1 file changed, 4 insertions(+)
>>>>
>>>> diff --git a/xf86drm.c b/xf86drm.c
>>>> index b5a174b..4a31019 100644
>>>> --- a/xf86drm.c
>>>> +++ b/xf86drm.c
>>>> @@ -63,7 +63,9 @@
>>>>
>>>>  #include "xf86drm.h"
>>>>  #include "libdrm_macros.h"
>>>> +#if defined(UDEV)
>>> The macro you're looking for (here and below) is #if HAVE_LIBUDEV.
>>>
>>
>> I'm not sure it's right using HAVE_LIBUDEV instead of UDEV because
>> currently UDEV is used from .c file but HAVE_LIBUDEV is not.
>>
> I'm afraid that I giggled a bit while I read this. Surely you know the
> difference between udev and libudev, and after a brief inspection of
> the code, original and newly added, you can see that it differs
> significantly. Additionally the newly added LIBUDEV_{CFLAGS,LIBS}
> should be a nice give-away :-)
> 

Thanks for pointing that.

> That aside, I'll send a revert in a second as mentioned previously.
> 

Good. Thanks.

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

      reply	other threads:[~2015-06-01  2:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28  0:56 [PATCH] xf86drm: fix build error by udev dependency Joonyoung Shim
2015-05-28  1:04 ` Deucher, Alexander
2015-05-28  8:53 ` Zhou, Jammy
2015-05-28 13:02 ` Emil Velikov
2015-05-29  6:34   ` Joonyoung Shim
2015-05-30 13:02     ` Emil Velikov
2015-06-01  2:52       ` Joonyoung Shim [this message]

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=556BC8EF.2000403@samsung.com \
    --to=jy0922.shim@samsung.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox