Bug 112655 – Excel import issue in OO.o 2.0 caused by -O2 compilation flag

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Eric Ding 2005-11-15 15:50:37 UTC]

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.

[Comment 1 Andreas Proschofsky (RETIRED) 2005-11-15 22:21:05 UTC]

I've added -fno-strict-aliasing to the forced CFLAGS in the ebuild now, thanks
for reporting

[Comment 2 Eric Ding 2005-11-17 06:53:18 UTC]

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.

[Comment 3 Eric Ding 2005-11-17 10:07:06 UTC]

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.

[Comment 4 Jakub Moc (RETIRED) 2005-11-21 16:46:56 UTC]

*** Bug 113209 has been marked as a duplicate of this bug. ***

[Comment 5 Jakub Moc (RETIRED) 2005-12-20 03:44:05 UTC]

*** Bug 116149 has been marked as a duplicate of this bug. ***