Summary: | Mesa build errors using build.sh script | ||
---|---|---|---|
Product: | Mesa | Reporter: | David <jdc843> |
Component: | Other | Assignee: | mesa-dev |
Status: | RESOLVED WONTFIX | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
David
2011-06-10 17:39:06 UTC
This looks like you don't have the Xlib headers installed. I don't know what the problem is, but I don't think it's in Mesa's build system. This issue is NOT resolved. Matt Turner wrote : "This looks like you don't have the Xlib headers installed." Read what I wrote : "The problem has to do with gcc not finding the X headers that were installed by build.sh." That means that the Xlib headers ARE installed. Every other package used by the build script can find those headers without problems. Only mesa has this problem. Try it yourself. Use build.sh to install X into /opt/X 14 months to respond to my bug report. Someone must be busy. Better late than never :) Have you tried this recently without setting INCLUDE_DIRS? The first one in src/egl/main/eglapi.c _should_ be fixed now since XCB_DRI2_CFLAGS are added when building this file and your log shows you got XCB_DRI2. For the second one, I think a small patch is needed to make sure that WL_EGL_PLATFORM is defined when building for wayland. Otherwise eglplatform.h will fall diff --git a/src/gallium/state_trackers/egl/common/native_wayland_drm_bufmgr_hel index 4365553..e38586b 100644 --- a/src/gallium/state_trackers/egl/common/native_wayland_drm_bufmgr_helper.c +++ b/src/gallium/state_trackers/egl/common/native_wayland_drm_bufmgr_helper.c @@ -7,6 +7,7 @@ #ifdef HAVE_WAYLAND_BACKEND +#include <wayland-egl.h> #include <wayland-server.h> #include <wayland-drm-server-protocol.h> Can you try this fix? src/gallium/state_trackers/egl/Makefile looks like it might need some other fixes, too. I'd also just like to quickly say that this situation creeps in frequently because almost everyone doing graphics development has /usr/include/X11/Xlib.h installed and doesn't notice when the build system is ignoring their just installed copy. So, it is helpful for you to report these issues to help them get resolved. We don't want to be preferring the system headers to the just installed headers. (In reply to comment #2) > This issue is NOT resolved. > > Matt Turner wrote : "This looks like you don't have the Xlib headers > installed." > > Read what I wrote : "The problem has to do with gcc not finding the X headers > that were installed by build.sh." > > That means that the Xlib headers ARE installed. Every other package used by the > build script can find those headers without problems. Only mesa has this > problem. > > Try it yourself. Use build.sh to install X into /opt/X > > 14 months to respond to my bug report. Someone must be busy. Better late than > never I think Bug 37423 is a duplicate, but I cannot remember which configuration switches I changed at that time to solve the problem. Today I cannot verify that bug any longer, with my compile script definitely the right headers are included. Add "-H" to CFLAGS CXXFLAGS, redirect everything to a file and use grep to find problems. If you build to a dir somewhere beneath /home, you could use e.g. buildscript &> buildlog cat buildlog | grep -n "/usr/include/X11" | grep -v home As -H, -v and similar flags that increase the verbosity of gcc can break xorg module loading you probably have to include a Section "Module" somewhere in your configuration if you want to use the compiled server or you have to rebuild without those flags. cu, Knut |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.