On Thu, May 17, 2012 at 4:04 AM, billywhizz <[email protected]> wrote: > thanks guys. yes, it looks like that's the issue. it works for me if i > change the configure to enable strict aliasing on my gcc which is 4.4.4 but > i'm not sure if enabling strict aliasing is going to cause other issues as > there were tons of warnings during the build... i guess upgrading gcc is the > definitive way to solve the issue?
Either that or compiling with -O0. :-) I haven't seen the issue with clang or gcc 4.6 / 4.7.
