Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | STLport4 on Solaris - not building | ||
---|---|---|---|
Product: | Build Tools | Reporter: | issues@www <issues> |
Component: | code | Assignee: | sander_traveling |
Status: | CLOSED FIXED | QA Contact: | issues@www <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues |
Version: | 625 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Solaris | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
issues@www
2001-04-11 22:27:39 UTC
Markus, this is the right place to complain. I forward this to our Solaris-builder. Sander, are you a guru? ;-) I tried now to build with WS 5.0 (latest patches from http://access1.sun.com/forte/workshop5-patches.html), it's now building. Since WS 6U1 is required it should be possible to build STLport 4.0 (or greater) with this compiler. If you need more information please contact me. But it *IS* possible to build STLport4 with WS6U1 - just make sure your amend include path the makefile to point at /usr/include Strictly speaking, this is a STLport4 (distribution) bug, but oh well... Clsoe the issue if this fixes it. sorry, but really don't get it... *sigh* The path is set to STL_INCL= -I. -I${PWD}/../stlport I tried all variants, at first position, at last, in the middle. It then complains about a missing <stl/_config.h> and <complex> that is in ../stlport so this path _must_ be included. But including that gives me the stated error. I think you asume that 6U1 comes with its own STL implementation of certain headers that should be used right? Couldn't this have something to do with the marko D__USE_SGI_STL_OWN_IOSTREAM? Or with -library=%none%,Crun ? I'm not soooo deep into this compiler.. *deep-sigh* If you take a look at the docs, they would tell you to put a /SC5 after I${PWD}/../stlport WOW, it's building! STL_INCL= -I/usr/include -I. -I${PWD}/../stlport/SC5 is what I set. IMHO this should be add to the build documentation. Thank you _very_ much for you help! As agreed on I will close these resolved fixed issues now. If you have trouble with that, please re-open the issue. As agreed on I will close these resolved fixed issues now. If you have trouble with that, please re-open the issue. |