Hello folks,

I'm getting a weird GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT status on an FBO that contains only a depth attachment. This didn't happen on my OSX station, so I suspect Linux drivers to be at fault. Here is what apitrace thinks is going on.
Texture & FBO creation:
Code :
529 glBindTexture(target = GL_TEXTURE_2D, texture = 37)
530 glTexImage2D(target = GL_TEXTURE_2D, level = 0, internalformat = GL_DEPTH_COMPONENT, width = 512, height = 512, border = 0, format = GL_DEPTH_COMPONENT, type = GL_UNSIGNED_BYTE, pixels = NULL)
531 glGenFramebuffers(n = 1, framebuffers = &4)
Framebuffer binding:
Code :
1134 glBindFramebuffer(target = GL_DRAW_FRAMEBUFFER, framebuffer = 4)
1135 glFramebufferTexture(target = GL_DRAW_FRAMEBUFFER, attachment = GL_DEPTH_ATTACHMENT, texture = 37, level = 0)
1136 glDrawBuffer(mode = GL_ZERO)
1137 glCheckFramebufferStatus(target = GL_DRAW_FRAMEBUFFER) = GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT
The description for this FBO status is "No images are attached to the framebuffer". In my case, there is clearly an image (depth texture) attached to it, so the status is at least misleading.

System Info:
Linux mezon 3.8.10-1-ARCH #1 SMP PREEMPT Sat Apr 27 12:36:59 CEST 2013 x86_64 GNU/Linux
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.1.1