Summary: | git mesa fails to build | ||
---|---|---|---|
Product: | Mesa | Reporter: | Jos van Wolput <wolput> |
Component: | GLX | Assignee: | mesa-dev |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Jos van Wolput
2012-05-29 20:49:00 UTC
Can you provide your ./configure arguments so we can maybe reproduce the failure? Do you have a range of commits for when the breakage was? (In reply to comment #1) No more build failure with the latest git-151bf6e. (In reply to comment #1) > Can you provide your ./configure arguments so we can maybe reproduce the > failure? Do you have a range of commits for when the breakage was? Well, I have the exact same issue with latest GIT. Here it's my configure: ./configure --prefix=/usr/xorg --libdir=/usr/xorg/lib64 --with-dri-drivers=i965 --with-gallium-drivers="" --enable-texture-float Any hints? (In reply to comment #3) > (In reply to comment #1) > > Can you provide your ./configure arguments so we can maybe reproduce the > > failure? Do you have a range of commits for when the breakage was? > > Well, I have the exact same issue with latest GIT. Here it's my configure: > > ./configure --prefix=/usr/xorg --libdir=/usr/xorg/lib64 > --with-dri-drivers=i965 --with-gallium-drivers="" --enable-texture-float > > Any hints? The original problem was resolved nearly two years ago, I find it surprising that you're having the "exact same issue". Would be better if you open fresh bug report, and provide all the information in there. The following would be nice to have * the full configure/build log (please attach as plain text) * the configure options that you're using * the git sha, as "latest git" is an rapidly changing target. Thanks -Emil (In reply to comment #4) > The original problem was resolved nearly two years ago, I find it surprising > that you're having the "exact same issue". > > Would be better if you open fresh bug report, and provide all the > information in there. The following would be nice to have > * the full configure/build log (please attach as plain text) > * the configure options that you're using > * the git sha, as "latest git" is an rapidly changing target. > > Thanks > -Emil Ok, I'll open a new bug. |
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.