Comment # 14
on bug 56405
from Michel Dänzer
(In reply to comment #13) > These are the compile errors I get with the above mentioned commit. > The compile errors are fixed in the commit also mentioned above. One strategy for such cases is to look at the commit fixing the compile error and see if (part of) it can be applied on top of other commits to be tested for the bisect. > And the commit I related to the 8.0 tag by the date > does not compile either. So this was not a good starting point > in the first place. Indeed, you should never declare a commit good or bad if it doesn't even compile. :) > I guess it would be better to bisect between the mesa-8.0.4 and mesa-9.0 > tags. > If I try this git asks me to check a merge base first. Yes, that's how it deals with non-linear history (so you don't have to worry about that yourself). > This merge base dates back to January and it seams to have > a very different configure/build structure. Maybe it would be easier to just do manual builds instead of using PKGBUILD for the bisect? You can point to the directory containing the manually built r600_dri.so with the environment variable LIBGL_DRIVERS_PATH. You may also want to set LIBGL_DEBUG=verbose to verify it's picking up the expected r600_dri.so. Also, especially for older commits, you may need to run make clean or even autogen.sh between bisection steps to prevent inconsistent builds.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
