| Summary: | kde-base/krfb-4.3.2: fails on build "X11/extensions/XTest.h: No such file or directory" | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Martin Walch <walch.martin> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | rudi.strasser |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
/var/tmp/portage/kde-base/krfb-4.3.2/temp/build.log
/var/tmp/portage/kde-base/krfb-4.3.2/temp/environment |
||
|
Description
Martin Walch
2009-10-14 20:39:26 UTC
Created attachment 207143 [details]
/var/tmp/portage/kde-base/krfb-4.3.2/temp/build.log
Created attachment 207144 [details]
/var/tmp/portage/kde-base/krfb-4.3.2/temp/environment
This problem comes from using x11-proto/xextproto-7.1.1 - XTest.h (together with many other headers) has been split into other header files. + 27 Oct 2009; Samuli Suominen <ssuominen@gentoo.org> krfb-4.3.2.ebuild: + Missing x11-libs/libXtst depend wrt #289104, thanks to Mr. Anderson for + reporting. ssuominen@unique /tmp/kdenetwork-4.3.2/krfb $ qfile -v XTest.h x11-libs/libXtst-1.1.0 (/usr/include/X11/extensions/XTest.h) ssuominen@unique /tmp/kdenetwork-4.3.2/krfb $ qlist -CIv libXext x11-libs/libXext-1.1.1 ssuominen@unique /tmp/kdenetwork-4.3.2/krfb $ grep ^#include * |grep -i xtest events.cpp:#include <X11/extensions/XTest.h> krfbserver.cpp:#include <X11/extensions/XTest.h> why do I still experience this problem ? Isn't the issue fixed ? (In reply to comment #5) > why do I still experience this problem ? Isn't the issue fixed ? Simply remerging (with oneshot) xextproto solved it for me. > emerge -a1tv xextproto Stupid shit though. (In reply to comment #6) > (In reply to comment #5) > > why do I still experience this problem ? Isn't the issue fixed ? > > Simply remerging (with oneshot) xextproto solved it for me. > > emerge -a1tv xextproto > Stupid shit though. I can imagine this happens when switching between different versions of X (especially switching to older versions) while collision-protect is not activated, because I do not see any explicit block between <xextproto-7.1.0 and libXtst. (Well, I am not sure about this.) |