Issue 92066 - upgrade to STLport-4.5 for Solaris
Summary: upgrade to STLport-4.5 for Solaris
Status: CONFIRMED
Alias: None
Product: utilities
Classification: Unclassified
Component: code (show other issues)
Version: DEV300m26
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact: issues@tools
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-24 08:16 UTC by Stephan Bergmann
Modified: 2017-05-20 11:33 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Stephan Bergmann 2008-07-24 08:16:30 UTC 
Issue 83545 appears to be caused by an error in STLport-4.0 still used on
Solaris (while virtually all other platforms use STLport-4.5, see
stlport/makefile.mk:1.44).  While it appears that a simple workaround fixed
issue 83545 for now, it would probably be better to upgrade Solaris to use
STLport-4.5, too.
Comment 1 christianlins 2008-12-10 13:14:43 UTC 
Isn't it possible to replace STLport with Apache stdcxx (http://
stdcxx.apache.org/) ? 
It seems robust, clean and builds well especially on (Open)Solaris.
Comment 2 jens-heiner.rechtien 2008-12-10 13:38:24 UTC 
The biggest problem with changing the STL implementation is that we may break
existing plugins and extensions. It might work to upgrade from STLport 4.0 to
4.5 without such breakage, but upgrading to Apache stdcxx (which is Rogue Wave
based AFAIK) will certainly break binary compatibility. The question is, can we
do this?
Comment 3 christianlins 2008-12-10 14:14:10 UTC 
Binary compatibility is a fine thing, but compatibility at any cost (patching 
STLport4 until the end of all days...) is imho no opinion.

From my point of view (which may be limited *g*) STLport4.x is of horrible code 
quality and emits lots of warnings on new compilers (there are some issues to 
this point).

AFAIK Sun Studio is moving towards Apache stdcxx as their default STL.
Comment 4 jens-heiner.rechtien 2008-12-10 14:28:24 UTC 
Well, we can try it out with the 64 bit port, since we don't have any release
there yet. Otherwise, I would absolutely love to not consider binary
compatibility. It's a pity that this thing didn't emerge in time for OOo-3.0. As
for SunStudio, the decision to go with the Apache stdcxx - which is very
laudable - must be pretty new ... we asked them in the summer about their plans
and they didn't even mentioned Apache stdcxx ...
Comment 5 Marcus 2017-05-20 11:33:30 UTC 
Reset assigne to the default "issues@openoffice.apache.org".