Hi,
there is not yet a need to drop gcc-3.4 support I think, the usual
compile problems happen with gcc-3.3 or older versions. GCC made a major
(and very necessary) parser update from 3.3 to 3.4 and should have
bumped up the major version at that time.
We have discussed dropping gcc-3.3 support for quite some time now, but
we refrained from officially obsoleting it because OS/2 and MACOSX 10.3
support still depend on gcc-3.3, at least according to this list:
http://wiki.services.openoffice.org/wiki/Compiler_versions_used_by_port_maintainers_and_release_engineers
The deal up to now was, that for active development we don't care much
about testing buildability with the stoneage gcc-3.3 versions but would
accept patches from the port-maintainers to re-enable building with it.
It was also understood that we wouldn't make sweeping changes to
accommodate gcc-3.3 anymore. Certainly a gcc-3.3 build failure is *no*
reason for a Prio 1 task.
Regarding gcc-3.4: it seems that older *BSD still rely on gcc-3.4
support, but I don't know if this is still correct and if they can't
upgrade to something a bit more recent.
My suggestion:
- declare gcc-3.3 as not longer supported, patches aren't any longer
accepted
- declare gcc-3.4 as obsolete, patches will be accepted up to including
OOO330. Build breakers can't be flagged as "Prio 1", fixes will have to
come from the port maintainers using this obsolete version as most
developers will not have a way to fix or even to verify the build problem.
Comments? I would especially like to hear from the port maintainers.
Regards,
Heiner
Martin Hollmichel wrote:
Hi,
obviously OOo doesn't compile any longer with gcc3, see
http://qa.openoffice.org/issues/show_bug.cgi?id=95511, should we now
officially drop gcc3 ?
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
