Doesn't build after opengl upgrade

[go-gl-legacy]

Doesn't build after opengl upgrade

[bytbox]

(This is go 1.0.3.)

[pwaller]

Does it build if you comment out lines 4 and 5 of gl.h?

[bytbox]

Close, but no cigar.

# github.com/go-gl/gl
could not determine kind of name for C.glVertexAttrib4fv
could not determine kind of name for C.glVertexAttrib1f
could not determine kind of name for C.glVertexAttrib2fv
could not determine kind of name for C.glVertexAttribPointer
could not determine kind of name for C.glVertexAttrib1fv
could not determine kind of name for C.glVertexAttrib3f
could not determine kind of name for C.glVertexAttrib3fv
could not determine kind of name for C.glVertexAttrib4f
could not determine kind of name for C.glVertexAttrib2f
could not determine kind of name for C.glEnableVertexAttribArray
could not determine kind of name for C.glDisableVertexAttribArray

[pwaller]

What versions of glew and gl do you have installed on your system? Can you give the vitals of your archlinux install so that it might be possible to try and reproduce it?

[bytbox]

On Mon, 8 Apr 2013, Peter Waller wrote:

What versions of glew and gl do you have installed on your system? Can you
give the vitals of your archlinux install so that it might be possible to
try and reproduce it?

mesa 9.1.1
mesa-libgl 9.1.1
glew 1.9.0

Scott Lawrence

[pwaller]

@banthar, do you understand what's happening here?

[pwaller]

I figured it out. It's nothing to do with OpenGL. The problem stems from this go/gcc bug. I'm afraid we can't do anything from our side to fix this. Your only hope is to use go tip when they fix it, or stick to gcc < 4.8 for the time being.

I'm closing this one invalid from our side, but feel free to report back if there is more information or my analysis is incorrect (such as this being fixed upstream).

[bytbox]

Analysis makes sense to me (only looked at it briefly though). Thanks
anyway.

On Thu, 11 Apr 2013, Peter Waller wrote:

I figured it out. It's nothing to do with OpenGL. The problem stems from this go/gcc bug. I'm afraid we can't do anything from our side to fix this. Your only hope is to use go tip when they fix it, or stick to gcc < 4.8 for the time being.

I'm closing this one invalid from our side, but feel free to report back if there is more information or my analysis is incorrect (such as this being fixed upstream).

---

Reply to this email directly or view it on GitHub:
go-gl/gl#99 (comment)

Scott Lawrence