On Thu, Aug 21, 2008 at 6:09 PM, Caolan McNamara <[EMAIL PROTECTED]> wrote:
> Those actual warnings are basically spurious, ignore them. Thanks. It is simple. But, I know that your particular compiler, given as it is equivalent to > the RHEL-5 gcc, actually probably *does* has a bug with visibility which > IIRC may cause OOo to crash when it loads some old .sdw files, the > workaround it to disable visibility or to apply the > openoffice.org.2.0.3-dangerousvisibility.patch patch found in the > RHEL-4/CentOS openoffice.org src.rpm. It's pretty uncommon, but it can > happen. If you are just building OOo for hacking around with, then I > wouldn't bother changing your compiler for it. Where is the patch or src.rpm? > I don't think I've met a compiler yet that doesn't have *some* bug that > has affected openoffice.org in some way:-), but I'm pretty happy with > gcc 4.3.0/4.3.1 whose only known bug that has affected me is with > -fasynchronous-unwind-tables on i386 which isn't enabled by default on > that architecture anyway. As you recomended,I am compiling gcc 4.3.1 on my machine which will keep me busy for a while until I get back. In this way, I will have someone to bug when 4.3.1 does not work well :P. -- Best Regards, Nguyen Hung Vu ( Nguyễn Vũ Hưng ) [EMAIL PROTECTED] <[EMAIL PROTECTED]>, YIM: vuhung16 , Skype: vuhung16dg Japan through an eye of a gaijin: http://www.flickr.com/photos/vuhung/tags/fav/
