I encountered an issue with importing a particular Excel file into OpenOffice.org, in my case built from source on Gentoo Linux. Filing a defect with the OO.o team led us to conclude that the problem is with my particular optimization flags. I don't have anything particularly aggressive in my CFLAGS, but I do have -O2 in there. It turns out that the -fstrict-aliasing optimization that's turned on by that optimization level is causing problems; adding -fno-strict-aliasing per one of the OO.o team members' suggestion resolved the issue I was seeing. Should Gentoo's ebuild of openoffice 2.0 include this flag as well, as (for example) the freetype2 ebuild does? See http://qa.openoffice.org/issues/show_bug.cgi?id=57790 for more details regarding this issue.
I've added -fno-strict-aliasing to the forced CFLAGS in the ebuild now, thanks for reporting
One of the OO.o developers just posted a patch that should make the CFLAGS change unnecessary. See the OO.o bugs database link in the original description, or get the patch directly from: http://www.openoffice.org/nonav/issues/showattachment.cgi/31581/i57790.patch I haven't yet had a chance to try a build with this patch, though I've no reason to disbelieve that it will resolve the issue.
Hmm... a later post in the OO.o database indicates that it's probably wiser simply to keep -fno-strict-aliasing for now. So I think it's safe to ignore my last post about the particular patch.
*** Bug 113209 has been marked as a duplicate of this bug. ***
*** Bug 116149 has been marked as a duplicate of this bug. ***
