Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | cannot complete the build on slackware64-current linux | ||||||
---|---|---|---|---|---|---|---|
Product: | General | Reporter: | yury_t <yury.tarasievich> | ||||
Component: | code | Assignee: | AOO issues mailing list <issues> | ||||
Status: | UNCONFIRMED --- | QA Contact: | |||||
Severity: | Normal | ||||||
Priority: | P5 (lowest) | CC: | petko | ||||
Version: | 4.2.0-dev | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Linux 64-bit | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
yury_t
2019-11-06 20:35:49 UTC
Created attachment 86758 [details]
patch for the problem with files generated from writerfilter/source/ooxml
Hi, we just had a discussion about this issue on development mailing list. The issue occurs when not compiled in gnu++98 mode. Since the code seems that it is not used anywhere we have commented it out in trunc (4.5.0) in probably a later commit. I am currious we accept changes now via github. Do you prefer bugzilla or is github also an option you would use in the future? I've browsed the discussions you mention. The 1st correction (x(d.x) thingy) is trivial, indeed. However, I didn't see anything about the 2nd one (first-time comparisons in XSLT failing), while this might be indicating more serious problems present, caused by the newer C++ standard being used in building. I understand the build system uses its own 'xsltproc' instance? As for the bug reporting, I'd prefer Bugzilla. I'm not what you'd call 'a real developer' and I don't understand well git's branching/merging stuff (if at all); also Github's issues tracking system seems rather inconvenient to me. I could post brief stuff to the -devs mailing list, too (like some notes on dependencies order), if someone's watching. |