Christos, You wrote: > That is turned on with MKDEBUG right?
Yes. Here's the full build.sh command line: time ./build.sh -j 4 -D /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/destdir -R /bracket/i386-debug/test/2014.12.25.08.11.09/release -T /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/tools -O /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/obj -m i386 -V TMPDIR=/tmp -V MKDEBUG=YES -V MKREPRO=YES -x -U release sourcesets iso-image-source > If you build inside the gallium directory and make install there don't you get > the r*.debug files installed? I do... Do you mean like this? This was run in the tree left from a failed automated build: guido /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/src/external/mit/xorg/lib/gallium $ /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/tools/bin/nbmake-i386 guido /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/src/external/mit/xorg/lib/gallium $ /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/tools/bin/nbmake-i386 install # install /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/destdir/usr/X11R7/lib/modules/dri/gallium_dri.so.0 /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/tools/bin/i486--netbsdelf-install -U -M /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/destdir/METALOG -D /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/destdir -h sha256 -N /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/src/etc -c -r -o root -g wheel -m 444 gallium_dri.so.0 /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/destdir/usr/X11R7/lib/modules/dri/gallium_dri.so.0 /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/tools/bin/i486--netbsdelf-install -U -M /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/destdir/METALOG -D /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/destdir -h sha256 -N /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/src/etc -l s -r gallium_dri.so.0 /tmp/bracket/build/2014.12.25.08.11.09-i386-debug/destdir/usr/X11R7/lib/modules/dri/gallium_dri.so I guess that's a "no" (but I'm confused as to how it is relevant). Looking at the full build log from the automated build, the only place where the string "r200_dri.so.0.debug" occurs is in the "Files in flist but missing from DESTDIR" error message, so it would appear that it is not only not being installed, but not being built, either. -- Andreas Gustafsson, g...@gson.org
