Hi Michael,
On Thu, Apr 07, 2011 at 04:16:28PM +0100, Michael Meeks wrote:
On Wed, 2011-04-06 at 22:31 +0200, Francois Tigeot wrote:
CVER is defined in set_solenv.in and propagated in form of defines to the
entire source tree.
We're not worried about the Solaris build - we don't ship on that
platform, so feel free to ignore that.
Hmm, okay.
No developpers, no users, no problems :p
I've pushed a few commits to reduce C52 usage.
I've found it is almost unused expect in the following cases
- when set to C52 (version 5.2 of a solaris-specific compiler)
- when set to M1500 or M1600 (Microsoft Visual Studio compilers ?)
I guess removing the -DCVER in the cflags would be fine if we can show
there is no source using it.
Hopefully it could be done soon.
How often is opengrok refreshed ? It's quite good to find that sort of
strings.
Could a Solaris user confirm whether C52 is indeed completely obsolete
or not in the year 2011 ?
I would just ignore it :-) when the Illumos (the only Solaris I care
about personally) guys get to building LibreOffice, I imagine they will
use gcc (free software) anyway.
You mean OpenIndiana ?
AFAIK, Illumos is a sort of Linux/GNU team maintaining what was the old
OpenSolaris kernel and associated userland tools.
We then have different projects building on this base to produce complete
distributions. There's Nexenta and OpenIndiana I'm aware of. Nexenta is a
storage-server oriented system so they probably won't care.
That leaves OpenIndiana: http://openindiana.org/
--
Francois Tigeot
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.