Summary: | Build failures: glsl_lexer.cc & glsl_parser.cc don't exist | ||
---|---|---|---|
Product: | Mesa | Reporter: | Darren Salt <bugspam> |
Component: | Mesa core | Assignee: | mesa-dev |
Status: | RESOLVED NOTABUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Darren Salt
2012-07-25 22:43:28 UTC
Presumably this is with the latest git master? Have you done make clean/git clean? Also, what version of automake do you have? The old *.cpp files still existing was what caused this for me, and removing them fixed it. It was git master, yes. I use lightly-hacked Debian build scripts to do the build. I'd not done a git clean due to the debian directory; however, I've now removed those two files. (I wonder if they were implicated in causing rendering brokenness here.) More information. make[5]: *** No rule to make target `../../../../../src/mesa/libdricore/../../glsl/glsl_lexer.cc', needed by `glsl_lexer.lo'. Stop. make[5]: Leaving directory `/.../mesa/build/dri/src/mesa/libdricore' [...] $ find -name glsl_lexer.cc ./build/swx11+glu-static/src/glsl/glsl_lexer.cc ./build/dri/src/glsl/glsl_lexer.cc ./build/swx11+glu/src/glsl/glsl_lexer.cc $ I'd say that out-of-tree builds are currently broken. (In reply to comment #4) > More information. > > make[5]: *** No rule to make target > `../../../../../src/mesa/libdricore/../../glsl/glsl_lexer.cc', needed by > `glsl_lexer.lo'. Stop. > make[5]: Leaving directory `/.../mesa/build/dri/src/mesa/libdricore' > [...] > $ find -name glsl_lexer.cc > ./build/swx11+glu-static/src/glsl/glsl_lexer.cc > ./build/dri/src/glsl/glsl_lexer.cc > ./build/swx11+glu/src/glsl/glsl_lexer.cc > $ Run git clean -dfx and forget about it. > I'd say that out-of-tree builds are currently broken. As in... has never worked. That's one of the reasons we're doing this whole automake thing. |
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.