Comment 22 for bug 487038

This appears to have reared it's head in macports any chance of the patch being ported to it?

I'm getting the described error with revision 22756 from trunk.

Thanks, I can probably apply the patch locally if someone can give me a hint as to what the patch was that fixed it for the other two (I just don't know your code organization yet).