Comment 4 for bug 271933

There's something weirder going on here, because bug 449303 reported the same thing, also on a linux x86_64 platform.

I am bringing this back to UNCONFIRMED - gavin suspects that there's weirdness in the x86_64 compiler they are using, which breaks the way we're doing our string substitutions. That probably means the problem is upstream with the distros, but I'd like to keep the bug open until we can find an answer.

Anders, how would you feel about reporting this to the Ubuntu folks with reference to our suspicion, to see what they think?