Summary: | x11-libs/libvdpau-0.4 fails emerge, problem with include driproto2.h | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matthew <m.gentoo> |
Component: | New packages | Assignee: | Doug Goldstein (RETIRED) <cardoe> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | m.gentoo, x11 |
Priority: | High | ||
Version: | 10.0 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
output of 'emerge --info =x11-libs/libvdpau-0.4'
output of 'emerge -pqv =x11-libs/libvdpau-0.4' complete build log ebuild environment file |
Description
Matthew
2010-09-30 20:54:59 UTC
Created attachment 249112 [details]
output of 'emerge --info =x11-libs/libvdpau-0.4'
Created attachment 249114 [details]
output of 'emerge -pqv =x11-libs/libvdpau-0.4'
Created attachment 249116 [details]
complete build log
Created attachment 249117 [details]
ebuild environment file
$ grep deviceNameLength /usr/include/X11/extensions/dri2proto.h CARD32 deviceNameLength B32; $ qfile -v dri2proto.h x11-proto/dri2proto-2.3 (/usr/include/X11/extensions/dri2proto.h) What version of dri2proto you have? Does updating it, or any other installed x11-proto or x11-libs packages help? What about libX11? (In reply to comment #5) x11-proto/dri2proto-2.3, which I have reinstalled, to no avail. FYI, this was previously an 'un-loved' system, so there have been the usual update challenges, but I've been meticulous and careful, and this is the last thing that is really holding things up. A lot of packages end up wanting to update xorg-server and all things related (I have 1.5.3-r6), which I cannot do until this is solved. I'll try reinstalling all the x11-proto and x11-libs. Nevertheless, it is clear where the 'xDRI2ConnectReq' and 'xDRI2ConnectReply' structures are defined (in driproto2.h, and no place else that I can find), so what would cause the libvdpau build to not find those? Ugh! Apparently any package that include's driproto2.h has the same compile error (for example, media-libs/mesa) I re-emerged all x11-proto and x11-libs, but that didn't help. I'm looking at the libvdpau-0.4.ebuild... it does not include x11-proto/dri2proto as a dependency? As a matter of fact, it doesn't include x11-drivers/nvidia-drivers as a dependency? (although it does block certain versions of it). This isn't right, is it? OK, I successfully compiled by editing mesa_dri2.c (in work/libvdpau-0.4/src) and adding an explicit (not relative) include for dri2proto.h: -#include <X11/extensions/dri2proto.h> +#include </usr/include/X11/extensions/dri2proto.h> So is it an include path issue? I am not sure - notice the other includes in mesa_dri2.c... #include <X11/Xlibint.h> #include <X11/extensions/Xext.h> #include <X11/extensions/extutil.h> ...which obviously are working. It's almost as if another version of dri2proto.h is being included from somewhere else...AHA!! Found it! /usr/local/include/X11/extensions/dri2proto.h And of course now all is peachy with building. Hooray, the world makes sense now. So in conclusion: 1. Is it correct behavior to include /usr/local in the Make build paths? 2. Are the questions about libvdpau-0.4.ebuild legitimate? Thanks... (In reply to comment #8) > /usr/local/include/X11/extensions/dri2proto.h [...] > 1. Is it correct behavior to include /usr/local in the Make build paths? Yes, we cannot prevent it, but you *should not* install your own packages in /usr/local if you want to build your own packages as they *will* interfere with portage. Don't use /usr/local unless you know what you're doing. > 2. Are the questions about libvdpau-0.4.ebuild legitimate? Nope, the libvdpau ebuild is fine as-is. Thanks (In reply to comment #9) > (In reply to comment #8) > > 2. Are the questions about libvdpau-0.4.ebuild legitimate? > > Nope, the libvdpau ebuild is fine as-is. > Thank you for the reply. Of course I recognize your superiority in all things Gentoo, but for the benefit of user(s) interested in bettering their understanding, and potentially contributing in the future, would you be able to give some additional details, i.e., to those several questions I posed about the ebuild? Why is it fine to omit required dependencies (x11-proto/dri2proto and nvidia-drivers) from the libvdpau ebuild? |