https://bugs.freedesktop.org/show_bug.cgi?id=76577
--- Comment #5 from Dâniel Fraga <frag...@gmail.com> --- (In reply to comment #4) > Dâniel I'm kind of struggling to see(tested as well) how on earth did the > system header got included in your case, pending any funny options during > the compilation of gcc (other pieces of the toolchain). > > -I$(top_srcdir)/include is used prior to any other, which should handle > things correctly. Hmmm I have the following CPPFLAGS system-wide: -I/usr/xorg/include -I/usr/local/BerkeleyDB/include As far as I remember, some software I tried to compile had trouble to find the header files. Even with CPPFLAGS set, Mesa should look for their own header files first? Or not? At least here it seems CPPFLAGS will be at the end: http://www.gnu.org/software/automake/manual/html_node/Flag-Variables-Ordering.html I ran configure *without* CPPFLAGS and it worked (without your patch). So the problem is CPPFLAGS. The problem is: configure accepts CPPFLAGS. Does it mean that when CPPFLAGS is set it has precedence over Mesa include paths or no? Or Mesa should put CPPFLAGS *after* their own include paths? Maybe this would avoid this problem when user sets CPPFLAGS? -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
