All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Sedat Dilek <sedat.dilek@gmail.com>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] uxa: intel_sync_close() is only available when HAVE_DRI3
Date: Mon, 15 Sep 2014 13:12:08 +0200	[thread overview]
Message-ID: <CA+icZUWzF4tyH0qcVfbsDoVDDef6UHciF8sY1T+4BJrv73DKSA@mail.gmail.com> (raw)
In-Reply-To: <20140915075843.GS16043@nuc-i3427.alporthouse.com>

On Mon, Sep 15, 2014 at 9:58 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Sat, Sep 13, 2014 at 07:45:01PM +0200, Sedat Dilek wrote:
>> With LLVM v3.4.2 I got this error reported:
>> ...
>> intel_driver.c:1182:2: error: implicit declaration of function 'intel_sync_close' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
>>         intel_sync_close(screen);
>>         ^
>> In file included from intel_uxa.c:44:
>> ./intel_glamor.h:92:1: warning: unused function 'intel_glamor_fd_from_pixmap' [-Wunused-function]
>> intel_glamor_fd_from_pixmap(ScreenPtr screen,
>> ^
>> intel_driver.c:1182:2: note: did you mean 'intel_mode_close'?
>> ./intel.h:356:13: note: 'intel_mode_close' declared here
>> extern void intel_mode_close(intel_screen_private *intel);
>> ...
>>
>> Looking at <uxa/intel.h> intel_sync_close() is only available when DRI3 is supported.
>>
>> 516: #if HAVE_DRI3
>> 517: Bool intel_sync_init(ScreenPtr screen);
>> 518: void intel_sync_close(ScreenPtr screen);
>> 519: #endif
>>
>> Fix the issue by embedding intel_sync_close() with a HAVE_DRI3 ifdef check.
>>
>> Signed-off-by: Sedat Dilek <sedat.dilek@gmail.com>
>
> I went with a slightly different approach to keep the ifdefery out of
> the body:
>
> commit 067115a51b2646538a38ba603c688233c61e23cd
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date:   Mon Sep 15 08:44:41 2014 +0100
>
>     uxa: Stub out intel_sync_init|fini when not compiled in
>
>     In order to fix the build without DRI3, we need to stub out the
>     functions not compiled in, such as intel_sync_fini().
>
>     Reported-by: Sedat Dilek <sedat.dilek@gmail.com>
>     Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> Thanks for the bug report and patch,

Great!
I was thinking of adding stubs later, but I needed a fast dirty hack.

Thanks for the quick fix!

- Sedat -

      reply	other threads:[~2014-09-15 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-13 17:45 [PATCH] uxa: intel_sync_close() is only available when HAVE_DRI3 Sedat Dilek
2014-09-15  7:58 ` Chris Wilson
2014-09-15 11:12   ` Sedat Dilek [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=CA+icZUWzF4tyH0qcVfbsDoVDDef6UHciF8sY1T+4BJrv73DKSA@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@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.