Comment 17 for bug 207723

I know it does not really help but while googling on the subject two weeks ago, I found that *someone* (a developer) had posted a blog comment about the same symptom. The comment was about a mix of library versions that, when linked with Evo, would lead to the issue. Overall, special care had to be taken with the _exact_ lib versions.

I forgot to log the URL and can't find it back but I would suggest checking with the evo developers to know which exact libraries (version) evo depends on.