Comment 19 for bug 328035

On Fri, Mar 13, 2009 at 09:16:54AM -0000, Matt Zimmerman wrote:
> Steve, if you don't have any problems with you current test case, I
> think the next thing to try is a recompile of -1ubuntu5 with the current
> toolchain.

Well, the problem is present in the -1ubuntu4 build also, and the build log
for that version (built on Mar 2) shows that gcc-4.3 4.3.3-5ubuntu1 was used
for the build, postdating the fix in 4.3.3-3ubuntu4.

I was guessing that this was simply a case of the seemingly-innocuous change
exposing a bug elsewhere in the code, possibly a bug that upstream has
already fixed. I have it on my todo list to build the latest upstream and
see if the bug is reproducible there, but I understand this depends on
having a bleeding-edge libdrm first - I was waiting for a new upstream
version to be uploaded to jaunty, but Bryce says even this may not be new
enough. Bryce, do you have a pointer to the upstream git for libdrm?

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>