Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | next OpenOffice.org build on Linux with gcc3 (x86) | ||
---|---|---|---|
Product: | Build Tools | Reporter: | Martin Hollmichel <nesshof> |
Component: | code | Assignee: | sander_traveling |
Status: | CLOSED FIXED | QA Contact: | issues@tools <issues> |
Severity: | Trivial | ||
Priority: | P2 | CC: | issues |
Version: | current | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux, all | ||
Issue Type: | TASK | Latest Confirmation in: | --- |
Developer Difficulty: | --- | ||
Issue Depends on: | |||
Issue Blocks: | 2308 |
Description
Martin Hollmichel
2001-11-12 15:00:00 UTC
Hi, FYI, even now gcc 3.x can not be used to compile the latest glibc (they are still arguing over implementation details and where exceptions are handled and etc. See the GNU glibc alpha mailing list for more info about the incompatibilities between glibc 2.2.4 and earlier and gcc 3.X As I understand things there are also still gcc 3 issues in building the linux kernel the last time I looked. So I would not convert to using gcc 3.X *only* yet. I think it is more important to use the latest binutils and glibc to speed up OpenOffice startup using the prelinking support just added. You can do this using the current gcc. My 2 cents, Kevin ok, no problem with that, but may be we should be more precise: we want at least on the x86 platform use the gcc3 toolchain, other platform are to be evaluated. Hi Sander, are they problems with the configuration of gcc3 on LinuxX86, the status of this issue is still new ? changing status to accept -> the build was deliveered built with gcc3, but i want to check a couple of things the compiler should be switchable in the OOO_STBLE_1 build. Are you able to check in all your changes ? Has all work for this issue been done? yes, so closing veryfied As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. |