From: Paul Menzel <paulepanter@users.sourceforge.net>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] configure.ac: Do not include `x11-xcb`, `xcb-dri2` and `xcb-aux` in `XVMCLIB`
Date: Sun, 03 Feb 2013 13:29:04 +0100 [thread overview]
Message-ID: <1359894544.5048.16.camel@mattotaupa> (raw)
In-Reply-To: <20130203093213.GB9892@cantiga.alporthouse.com>
[-- Attachment #1.1: Type: text/plain, Size: 2170 bytes --]
Am Sonntag, den 03.02.2013, 09:32 +0000 schrieb Chris Wilson:
> The first patch looks fine (and I've applied it, thanks),
Thank you for the quick reaction.
> but I'm not convinced this one is safe.
>
> On Sat, Feb 02, 2013 at 11:00:15PM +0100, Paul Menzel wrote:
> > Date: Sat, 2 Feb 2013 20:33:36 +0100
> >
> > Building the package under Debian Sid/unstable, `dh_shlibdeps` informs
> > that `libI810XvMC.so.1.0.0` does not need to be linked against
> > `libX11-xcb.so.1`, `libxcb-dri2.so.0`, `libxcb-util.so.0` or
> > `libxcb.so.1` [1].
> >
> > $ debuild -b -us -uc
> > […]
> > make[1]: Entering directory `/src/xserver-xorg-video-intel'
> > dh_shlibdeps -- --warnings=6
> > dpkg-shlibdeps: Warnung: debian/xserver-xorg-video-intel/usr/lib/libI810XvMC.so.1.0.0 sollte nicht gegen libX11-xcb.so.1 gelinkt werden (es verwendet keines der Bibliotheks-Symbole)
> > dpkg-shlibdeps: Warnung: debian/xserver-xorg-video-intel/usr/lib/libI810XvMC.so.1.0.0 sollte nicht gegen libxcb-dri2.so.0 gelinkt werden (es verwendet keines der Bibliotheks-Symbole)
> > dpkg-shlibdeps: Warnung: debian/xserver-xorg-video-intel/usr/lib/libI810XvMC.so.1.0.0 sollte nicht gegen libxcb-util.so.0 gelinkt werden (es verwendet keines der Bibliotheks-Symbole)
> > dpkg-shlibdeps: Warnung: debian/xserver-xorg-video-intel/usr/lib/libI810XvMC.so.1.0.0 sollte nicht gegen libxcb.so.1 gelinkt werden (es verwendet keines der Bibliotheks-Symbole)
> > make[1]: Leaving directory `/src/xserver-xorg-video-intel'
> > […]
> >
> > Not populating `XVMCLIB` with `x11-xcb`, `xcb-dri2` and `xcb-aux` makes
> > the warnings go away and the libraries are still built without any
> > issues.
>
> Notice that the warning is only generated for I810XvMC and not for
> IntelXvMC which does use the DRI2 interface to pass along video objects.
I was surprised too that no error was generated. Do you have any idea
why compilations succeeds?
> Since XVMCLIB is shared between the two we would need to split out the
> I810XvMC dependencies from the IntelXvMC set first.
Thanks,
Paul
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2013-02-03 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 22:00 [PATCH 2/2] configure.ac: Do not include `x11-xcb`, `xcb-dri2` and `xcb-aux` in `XVMCLIB` Paul Menzel
2013-02-03 9:32 ` Chris Wilson
2013-02-03 12:29 ` Paul Menzel [this message]
2013-02-04 21:28 ` Julien Cristau
2013-02-05 23:42 ` Paul Menzel
2013-02-06 9:59 ` [PATCH v2 2/2] configure.ac: Split out XCB libraries from `XVMCLIB` into `XCB` Paul Menzel
2013-02-06 10:20 ` Chris Wilson
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=1359894544.5048.16.camel@mattotaupa \
--to=paulepanter@users.sourceforge.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox