Debug mesa
De HurdFr_Wiki.
Mesa FTBFS debugging (#358065)
Sommaire |
Quick investigation
BUILD_* variables
After having added some @echo calls before the first rule in debian/rules, it looks like all calculated BUILD_* variables are the same on linux and hurd. The only difference I see there is that DFB_MODULE_DIR is set to /usr/lib/directfb-0.9.25 on linux and is empty on hurd.
configs/*
configs/debian-dri contains the basic configuration (variable definitions) for the dri stuff. Noticeable here:
- LIBDRM_LIB = `pkg-config --libs libdrm` :
No package 'libdrm' found on hurd, -ldrm on linux;
=> That is normal, there's no libdrm-dev on hurd.
- GL_LIB_DEPS = `pkg-config --libs x11 xext xxf86vm` [...] :
No package 'xxf86vm' found on hurd; returns -lX11 -lXext -lXxf86vm on linux
=> That's not normal, libxxf86vm-dev provides the needed .pc, but is not installed via B-D...
However, apt-get installing it (manually) solves that matters for the time being.
=> Hmmm, I should have messed up things. On another box, it _is_ installed via B-D...
Forgot about that one...
configs/debian is included, but contains no problematic instructions.
configs/defaults is then included from that latter. The only warning I could see here is:
# external projects. This should be useless now that we use libdrm. DRM_SOURCE_PATH=$(TOP)/../drm
but as stated in the comment, that should be harmless.
select_target* "variables"
select_target_any
dh_listpackages -s | while read p ; do cut -f 1,3 -d ' ' debian/libdir.map | grep -w $p ; done returns the same result on both hurd and linux, 18 lines.
Adding | grep -v _ filters out 5 lines. Adding | cut -d ' ' -f 1 | sort -u (sorts and) filters out an only line: gl-debian-debug</nowiki>
