>> It's a little "less invasive". If it doesn't work (hidden compiler >> mystery....), just go ahead and push your patch. Cheers > I tried - still the same FTBFS with reference to a compiler bug. > Any other suggestions? :) Slavek, the problem is not in the C++ code, but clearly in the compiler. If you google a little you can see we are not the only one affected :) The problem is probably caused by the addition in: "[0 D.20205_111->m_sbyte+0 S1 A64]))" even though it is not clear to me why the compiler generate such code since I didn't see any addition in the C++ code. Since your patch works and it is quite simple, just push it. The comment in place will remind us of why the change was necessary. Cheers Michele