|
Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
| Summary: | build appears to assume gcc-2.95.2 | ||
|---|---|---|---|
| Product: | Build Tools | Reporter: | issues@www <issues> |
| Component: | code | Assignee: | Unknown <non-migrated> |
| Status: | CLOSED NOT_AN_OOO_ISSUE | QA Contact: | issues@www <issues> |
| Severity: | Trivial | ||
| Priority: | P3 | CC: | issues, sander_traveling |
| Version: | 613 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux, all | ||
| Issue Type: | DEFECT | Latest Confirmation in: | --- |
| Developer Difficulty: | --- | ||
|
Description
issues@www
2001-01-19 10:44:33 UTC
The code does NOT assume gcc 2.95.2 - it assumes a non-broken C++ compiler that supports all needed features. gcc 2.95.2 (and .3, which is btw. supported by configure since 613). Other suitable compilers are the Sun Workshop/Forte compilers 5.0 and 6 update 1. You should at least try to investigate the issue before filing an issue. Sander... sorry, Eazel may use their bugzilla tree differently. When in doubt we usually file the bug anyway (note my use of ambiguity, "appears to assume..."). The configure.in for 613 is laced with mention of requiring 2.95.2+ (implying that 2.95.3 should work), but does not succesfully locate 2.95.3 paths such as /usr/lib/gcc-lib/i386-linux/2.95.3. I believe there are ac macros that handle finding this path automatically, btw. Sorry, the body ('exteremly unpotrable', etc.) just came over as a bit strongly
worded. If configure does indeed not correctly detect gcc 2.95.3, please file a
new bug report for that - I'd rather leave this one as 'resolved invalid'.
You might also want to asisgn it directly to me.
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. First step in IssueZilla is unfortunately to set them to verified. 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. First step in IssueZilla is unfortunately to set them to verified. 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. First step in IssueZilla is unfortunately to set them to verified. 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. 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. |