To aleviate the problem that openoffice does not compile with the 3.4 compiler releases (not much we can do about it, fixing is nontrivial). I am working to get support working for automatically using the 3.3.4 compiler, where it will be specified as a dependency. There are a number of problems I encountered though: - A probably stale check on all libraries and binaries with broken stack protection build it (an annoyance only) - All .la files (like the kde ones) are reverted to this old compiler while it is only secondary. This backporting WILL break as the actual libraries were linked against the new libstdc++. Probably the fixing script should be fixed to check on the actual library version linked in the actual library. - The new compiler is automatically made the default compiler. Obviously this will completely defeat the purpose of having this gcc for openoffice only, and also will break many people's environments. When a second compiler is installed an it's version is smaller than the current one, it should only become the default compiler (automatically) when the new one is removed. (Manual override is no problem of course)
I don't think we plan on making a "secondary" compiler ever. We allow you to have multiple compilers installed that you can use as your system compiler. If you have a way we can sanely support this, let me know. Also, this is no longer an issue since openoffice works with newer versions of GCC as far as I am aware.
You are right that openoffice has no problems anymore. The issue of broken downgrading does however still remain. (Unless something changed). With openoffice no longer requiring a lower gcc version (at this moment) the downgrading behaviour is less problematic as it is no longer required.
(In reply to comment #2) > The issue of broken > downgrading does however still remain. (Unless something changed). Pretty sure this is fixed to. (In reply to comment #0) > - All .la files (like the kde ones) are reverted to this old compiler while it > is only secondary. This backporting WILL break as the actual libraries were > linked against the new libstdc++. Probably the fixing script should be fixed > to check on the actual library version linked in the actual library. Run fix_libtool_files.sh. In a perfect world, we would have a much better solution than this, but switching your system compiler across major versions and hoping everything will work is asking a bit much to begin with. > - The new compiler is automatically made the default compiler. Obviously this > will completely defeat the purpose of having this gcc for openoffice only, and > also will break many people's environments. This only occurs when the old compiler is removed, which in turn only happens when you are upgrading to a bug release version of your existing compiler. > When a second compiler is > installed an it's version is smaller than the current one, it should only > become the default compiler (automatically) when the new one is removed. > (Manual override is no problem of course) We don't switch across major versions since those are slotted, and you will only automatically be switched when the old profile is removed.
