Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


there is an issue with compiling Mozilla with the gcc compiler on
Solaris (unless they've fixed it in the last year) I think it's due to
the c++ compatibility issue with some standard Solaris libs compiled
with Sun studio.

I will try compiling without mozilla, using gcc (I'm stuck on the
stlport, which stops the xml2cmp compilation anyway)

Jon

On 25 January 2012 20:03, Michael Meeks <michael.meeks@suse.com> wrote:
Hi guys

       I was thrilled to read of your efforts trying to get LibreOffice going
on OpenIndiana; it'd be great to get any patches you have back into the
code.

       Having said that - I think we -really- want to discourage use of the
sunpro compiler, and I'd suggest trying to build with gcc/g++ and fixing
that. That is likelier to cause fewer problems in the longer run I think
(though we'll need to rip out a number of compiler conditionals for
solaris at the same time I think). We routinely find & have to
workaround compiler bugs, and the fewer compilers we have to support the
better.

       Anyhow - please do ask questions etc. here - hopefully we're a friendly
lot :-) I'd really recommend building from the "libreoffice-3-5"
code-branch, that is feature frozen and about to get released, whereas
3.4 is some rather ultra deep-frozen branch.

       All the best,

               Michael.

--
michael.meeks@suse.com  <><, Pseudo Engineer, itinerant idiot


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.