<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - A compilation error happen when update mesa from 10.6.7 to 11.0.2" href="https://bugs.freedesktop.org/show_bug.cgi?id=92293#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - A compilation error happen when update mesa from 10.6.7 to 11.0.2" href="https://bugs.freedesktop.org/show_bug.cgi?id=92293">bug 92293</a> from <a class="email" href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov <emil.l.velikov@gmail.com>"> Emil Velikov</a> <pre>(In reply to Neil Roberts from <a href="show_bug.cgi?id=92293#c2">comment #2</a>) > I think the general problem is that if you install an old version of Mesa > somewhere and then try and build a new version while specifying the install > prefix of the old version as an include path with -I in the CPPFLAGS then it > will end up picking up the old installed headers instead of the ones that > are internal to the Mesa source tree. In this case the problematic header is > GL/internal/dri_interface.h, but there are others. It doesn't seem like this > is such an unusual thing to do so it would be nice if it worked. > > Note, in this case it was being built out-of-tree, but I'm not sure if > that's necessary to replicate the bug. I've been building mesa OOT for 2+ years, and I'm afraid that I've not hit headers issues. If you can come up with some examples/how to, that'll be appreciated. There is some (re-)linking fun, when libtool 'inserts' -L/usr/lib prior to -L/custom/prefix, but that will require a massive rewrite on our side :'(</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>