Yes, its a fix that broke it :P. After going through what it does, it basically enables support for __thread if the compiler supports it, and in this case gcc *does* support it.
However, it looks like there's either a bug with the gcc __thread implementation, or how pixman uses __thread. Previously, such functionality looks like it would have defaulted to a pthread implementation.
Looks like this needs to be pushed upstream (somewhere), because the same bug exists up to the current HEAD and disabling __thread support fixes it.
I've found out what causes this bug; I found this bug not in wxRuby, but in wxLua---but its the same bug, using pixman 0.20.0 seems to fix it.
The offending commit (after trying each commit from 0.20.0 to 0.20.2 is: cgit.freedeskto p.org/pixman/ commit/ ?h=0.20& id=6718621c62ef 03d1dd71c34242a 873aba798e8aa
http://
Yes, its a fix that broke it :P. After going through what it does, it basically enables support for __thread if the compiler supports it, and in this case gcc *does* support it.
However, it looks like there's either a bug with the gcc __thread implementation, or how pixman uses __thread. Previously, such functionality looks like it would have defaulted to a pthread implementation.
Looks like this needs to be pushed upstream (somewhere), because the same bug exists up to the current HEAD and disabling __thread support fixes it.