You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Alexander Pyhalov <al...@rsu.ru> on 2014/08/01 17:27:27 UTC
Building OpenOffice on illumos with gcc
Hello.
I've just integrated OpenOffice component into OpenIndiana /hipster
illumos distribution. I'd like to share some patches and to ask if they
could be converted to bug reports, feature requests and which of them
can be integrated.
OpenIndiana distribution tries to be compatible with Solaris 11.
However, there are several distinctions, the main one is system
compiler. We use gcc (4.8) with illumos (former Sun Solaris) linker
instead of Sun Studio.
The work I've made was based on earlier work of Apostolos Syropoulos,
which he described here:
https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/ .
The full component is available here:
https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openoffice/openoffice
.
And patches are in "patches" subdirectory:
https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openoffice/openoffice/patches
.
I had to make about 20 changes.
01.use-illumos-ld.patch
OpenOffice configure script doesn't like illumos ld and GCC on Solaris,
so I relaxed this restriction.
02.use-gcc.patch
Patches to main solenv/* make files are mostly taken from Apostolos blog
(perhaps, with some corrections) and IIRC are based on Linux makefiles.
They are necessary to introduce Solaris/GCC platform.
03.g++-includes.patch
Our boost live in /usr/g++, so we have to teach OpenOffice to search it
there. We can't use CPPFLAGS, because this breaks icu compilation. It
would be perfect if we can provide boost path with configure switch.
04.gmake-j.patch
dmake is supposed to call gmake in several cases. But sometimes it calls
dmake or make and it doesn't like "-j" flags. Don't know why it happens.
So I just had to remove "-j" flags.
05.visibility.patch
Without this patch some symbols are hidden during sc compilation.
06.ignore_mapfiles.patch
Some mapfiles introduce symbols which are not present in OpenIndiana.
07.cstring.patch
Missing <cstring> includes.
08.adsyms.awk.patch
Complements 06.ignore_mapfiles.patch. _ZTI* symbols are not present in
result libraries.
09.libxmlsec-ldflags.patch
LDFLAGS are not passed during libxmlsec build
10.xinerama.patch
Two issues - 1) saldisp defines MAXFRAMEBUFFERS only for XSUN.
2) neither USE_XINERAMA_XORG nor USE_XINERAMA_XSUN are defined.
11.wmadaptor-gcc48.patch
It seems just gcc 4.8 doesn't like &const_cast<char*>(pText) construction.
12.undefine-macroses.patch
Some symbols used by OpenOffice are defined in our headers. Undefine them.
13.remove-studio-specific.patch
Studio flags are unconditionally passed to the compiler. Fix this.
14.webdav-apr.patch
On OpenIndiana we have /usr/apr/include, not /usr/include/apr. Also
runpaths for APR and APR-UTIL are missing. Perhaps, adding some switch
to set apr/apr-util runpath and include <header.h> instead of
<apr/header.h> would help here.
15.icu.patch (in fact, patch to patch :))
There are two issues.
1) in uperf.cpp _XOPEN_SOURCE_EXTENDED is defined. This hides some
symbols on Solaris/illumos. So, we don't receive _XPG6 and get an error
"Compiler or options invalid for pre-UNIX 03 X/Open applications \
and pre-2001 POSIX applications"
There's no need to define this guard on illumos.
2) We should add runpath to binaries, else compiling icu is linked to
system icu in /usr/lib (compiled with Studio) and we receive binaries
which are linked to both Studio and GCC C++ runtime simultaneously.
16.lstdc++.patch
Binaries are unconditionally linked to lCstd on Solaris. Fix this.
17.nss.patch
OpenOffice has hardcoded paths for nss libraries and headers. Set paths
to our paths. One more time when having configure switch is desirable.
18.sal_osl_unx.patch
1) One more define supposing that the only Solaris compiler is Studio
2) We (as MACOSX) also have posix_madvise (just cut&paste Apostolos'
change, don't know, why usual madvise fails to work, perhaps, missing
headers).
Post-install processing:
bootstraprc has incorrect UserInstallation setting and tries to write
user configs to installation directory (fix was taken from FreeBSD
port). Alsoe some binaries have incorrect runpaths. Fix this.
--
Best regards,
Alexander Pyhalov,
system administrator of Computer Center of Southern Federal University
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Building OpenOffice on illumos with gcc
Posted by Andrea Pescetti <pe...@apache.org>.
On 06/08/2014 Alexander Pyhalov wrote:
>>> [Andrea Pescetti]
>>> Alexander, thanks a lot for your work, and if you provide some basic
>>> information for an entry in http://www.openoffice.org/porting/ we can
>>> surely add it to that page.
> I don't know what information is needed. OpenIndiana /hipster illumos
> distribution uses oi-userland build system to package software.
> OpenOffice build files can be found here
> https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openoffice/openoffice
> Users of our distribution can just use system package manager to install
> pkg://openindiana.org/desktop/office/openoffice package.
Thanks, added to the above page. If you have any better links than the
one to Github we are using now (such as a link to
http://pkg.openindiana.org/dev/en/catalog.shtml or similar; I couldn't
locate this package there), just send it and we can modify the page
accordingly.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Building OpenOffice on illumos with gcc
Posted by Alexander Pyhalov <al...@rsu.ru>.
On 08/06/2014 11:09, Alexander Pyhalov wrote:
>
>> This is indeed the recommended way to contribute code. Apostolos, who
>> did the initial work, already stated in this thread that we are allowed
>> to use his work under the Apache license (the OpenOffice license terms),
>> so there are no other concerns.
>>
>> Alexander, thanks a lot for your work, and if you provide some basic
>> information for an entry in http://www.openoffice.org/porting/ we can
>> surely add it to that page. Even better, we can gradually integrate your
>> work so that it's not even a "port" any longer!
I don't know what information is needed. OpenIndiana /hipster illumos
distribution uses oi-userland build system to package software.
OpenOffice build files can be found here
https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openoffice/openoffice
Users of our distribution can just use system package manager to install
pkg://openindiana.org/desktop/office/openoffice package.
--
Best regards,
Alexander Pyhalov,
system administrator of Computer Center of Southern Federal University
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Building OpenOffice on illumos with gcc
Posted by Kay Schenk <ka...@gmail.com>.
On 08/06/2014 12:09 AM, Alexander Pyhalov wrote:
>
>> This is indeed the recommended way to contribute code. Apostolos, who
>> did the initial work, already stated in this thread that we are allowed
>> to use his work under the Apache license (the OpenOffice license terms),
>> so there are no other concerns.
>>
>> Alexander, thanks a lot for your work, and if you provide some basic
>> information for an entry in http://www.openoffice.org/porting/ we can
>> surely add it to that page. Even better, we can gradually integrate your
>> work so that it's not even a "port" any longer!
>>
>> Please make sure to "tag" issues appropriately, like prepending their
>> title with [ILLUMOS], so that we can easily see the global picture while
>> integrating them.
>
> Hello.
> I've reported most annoying issues here:
>
> https://issues.apache.org/ooo/show_bug.cgi?id=125361
> https://issues.apache.org/ooo/show_bug.cgi?id=125362
> https://issues.apache.org/ooo/show_bug.cgi?id=125363
> https://issues.apache.org/ooo/show_bug.cgi?id=125364
> https://issues.apache.org/ooo/show_bug.cgi?id=125365
> https://issues.apache.org/ooo/show_bug.cgi?id=125366
> https://issues.apache.org/ooo/show_bug.cgi?id=125368
> https://issues.apache.org/ooo/show_bug.cgi?id=125369
> https://issues.apache.org/ooo/show_bug.cgi?id=125370
> https://issues.apache.org/ooo/show_bug.cgi?id=125371
> https://issues.apache.org/ooo/show_bug.cgi?id=125372
> https://issues.apache.org/ooo/show_bug.cgi?id=125373
>
> I think that https://issues.apache.org/ooo/show_bug.cgi?id=125362 can be
> used as a covering issue.
>
> Also, note that I haven't tried to preserve Solaris/C52 port while doing
> this work, so some additional work is needed to allow Solaris/C52 and
> Solaris/GCC ports to coexist.
Thanks for documenting your patches this way. Hopefully, some of our
other Solaris developers will see this and test these out as well. And,
maybe some of them have some ideas about co-existing with Solaris
Studio, etc.
--
-------------------------------------------------------------------------
MzK
"For evil to flourish, it only requires good men to do nothing."
-- Simon Wiesenthal
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Building OpenOffice on illumos with gcc
Posted by Alexander Pyhalov <al...@rsu.ru>.
> This is indeed the recommended way to contribute code. Apostolos, who
> did the initial work, already stated in this thread that we are allowed
> to use his work under the Apache license (the OpenOffice license terms),
> so there are no other concerns.
>
> Alexander, thanks a lot for your work, and if you provide some basic
> information for an entry in http://www.openoffice.org/porting/ we can
> surely add it to that page. Even better, we can gradually integrate your
> work so that it's not even a "port" any longer!
>
> Please make sure to "tag" issues appropriately, like prepending their
> title with [ILLUMOS], so that we can easily see the global picture while
> integrating them.
Hello.
I've reported most annoying issues here:
https://issues.apache.org/ooo/show_bug.cgi?id=125361
https://issues.apache.org/ooo/show_bug.cgi?id=125362
https://issues.apache.org/ooo/show_bug.cgi?id=125363
https://issues.apache.org/ooo/show_bug.cgi?id=125364
https://issues.apache.org/ooo/show_bug.cgi?id=125365
https://issues.apache.org/ooo/show_bug.cgi?id=125366
https://issues.apache.org/ooo/show_bug.cgi?id=125368
https://issues.apache.org/ooo/show_bug.cgi?id=125369
https://issues.apache.org/ooo/show_bug.cgi?id=125370
https://issues.apache.org/ooo/show_bug.cgi?id=125371
https://issues.apache.org/ooo/show_bug.cgi?id=125372
https://issues.apache.org/ooo/show_bug.cgi?id=125373
I think that https://issues.apache.org/ooo/show_bug.cgi?id=125362 can be
used as a covering issue.
Also, note that I haven't tried to preserve Solaris/C52 port while doing
this work, so some additional work is needed to allow Solaris/C52 and
Solaris/GCC ports to coexist.
--
Best regards,
Alexander Pyhalov,
system administrator of Computer Center of Southern Federal University
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Building OpenOffice on illumos with gcc
Posted by Andrea Pescetti <pe...@apache.org>.
On 05/08/2014 Ariel Constenla-Haile wrote:
> On Tue, Aug 05, 2014 at 10:45:03AM +0400, Alexander Pyhalov wrote:
>> On 08/01/2014 19:27, Alexander Pyhalov wrote:
>>> I've just integrated OpenOffice component into OpenIndiana /hipster
>>> illumos distribution. I'd like to share some patches and to ask if they
>>> could be converted to bug reports, feature requests and which of them
>>> can be integrated.
>> Could someone comment this?
> You can report the bugs in Bugzilla https://issues.apache.org/ooo/
> attaching the patches in each bug.
This is indeed the recommended way to contribute code. Apostolos, who
did the initial work, already stated in this thread that we are allowed
to use his work under the Apache license (the OpenOffice license terms),
so there are no other concerns.
Alexander, thanks a lot for your work, and if you provide some basic
information for an entry in http://www.openoffice.org/porting/ we can
surely add it to that page. Even better, we can gradually integrate your
work so that it's not even a "port" any longer!
Please make sure to "tag" issues appropriately, like prepending their
title with [ILLUMOS], so that we can easily see the global picture while
integrating them.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Building OpenOffice on illumos with gcc
Posted by Ariel Constenla-Haile <ar...@apache.org>.
Hi Alexander,
On Tue, Aug 05, 2014 at 10:45:03AM +0400, Alexander Pyhalov wrote:
> On 08/01/2014 19:27, Alexander Pyhalov wrote:
> >Hello.
> >I've just integrated OpenOffice component into OpenIndiana /hipster
> >illumos distribution. I'd like to share some patches and to ask if they
> >could be converted to bug reports, feature requests and which of them
> >can be integrated.
>
> Could someone comment this?
You can report the bugs in Bugzilla https://issues.apache.org/ooo/
attaching the patches in each bug.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
Re: Building OpenOffice on illumos with gcc
Posted by Alexander Pyhalov <al...@rsu.ru>.
On 08/07/2014 02:42, Paul Gress wrote:
> On 08/ 6/14 02:01 AM, Alexander Pyhalov wrote:
>> On 08/06/2014 02:37, Paul Gress wrote:
>>> On 08/ 5/14 02:45 AM, Alexander Pyhalov wrote:
>>>> On 08/01/2014 19:27, Alexander Pyhalov wrote:
>>>>> Hello.
>>>>> I've just integrated OpenOffice component into OpenIndiana /hipster
>>>>> illumos distribution. I'd like to share some patches and to ask if they
>>>>> could be converted to bug reports, feature requests and which of them
>>>>> can be integrated.
>>>>
>>>> Could someone comment this?
>>>>
>>>
>>>
>>> Hi Alexander,
>>>
>>> I use Solaris 11.2. Is there a way to package this to install on 11.2?
>>> Maybe tarred?
>>
>> http://buildzone.oi-build.r61.net/openoffice.tar.gz
>>
>> I'm not sure it will work on Solaris 11 as is.
>>
>>
>
> Success, see below images. It appears to be functioning correctly as you can
> see there are no startup errors. Although I did notice one small nagging thing,
> the spell checker still doesn't work, as it stopped working also in 3.4. The
> last version it worked was in 3.3 compiled previously by Sun. Some people
> mentioned about Java labeling.
>
> Anyway, I'm going to place it into the /opt directory properly and use it. I'll
> report if there are any other problems.
>
For me spellchecker works if I install dictionaries from OO extensions site.
--
Best regards,
Alexander Pyhalov,
system administrator of Computer Center of Southern Federal University
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Building OpenOffice on illumos with gcc
Posted by Paul Gress <pg...@optonline.net>.
On 08/ 7/14 07:30 AM, Keith N. McKenna wrote:
>
> Paul;
> Most spell check problems can be solved by resetting the profile. See
> the tutorial on the forum at
> https://forum.openoffice.org/en/forum/viewtopic.php?f=74&t=12426#p58403 .
>
>
Solved, thanks very much
Re: Building OpenOffice on illumos with gcc
Posted by "Keith N. McKenna" <ke...@comcast.net>.
On 8/6/2014 6:42 PM, Paul Gress wrote:
> On 08/ 6/14 02:01 AM, Alexander Pyhalov wrote:
>> On 08/06/2014 02:37, Paul Gress wrote:
>>> On 08/ 5/14 02:45 AM, Alexander Pyhalov wrote:
>>>> On 08/01/2014 19:27, Alexander Pyhalov wrote:
>>>>> Hello.
>>>>> I've just integrated OpenOffice component into OpenIndiana /hipster
>>>>> illumos distribution. I'd like to share some patches and to ask if
>>>>> they
>>>>> could be converted to bug reports, feature requests and which of them
>>>>> can be integrated.
>>>>
>>>> Could someone comment this?
>>>>
>>>
>>>
>>> Hi Alexander,
>>>
>>> I use Solaris 11.2. Is there a way to package this to install on 11.2?
>>> Maybe tarred?
>>
>> http://buildzone.oi-build.r61.net/openoffice.tar.gz
>>
>> I'm not sure it will work on Solaris 11 as is.
>>
>>
>
> Success, see below images. It appears to be functioning correctly as
> you can see there are no startup errors. Although I did notice one
> small nagging thing, the spell checker still doesn't work, as it stopped
> working also in 3.4. The last version it worked was in 3.3 compiled
> previously by Sun. Some people mentioned about Java labeling.
>
Paul;
Most spell check problems can be solved by resetting the profile. See
the tutorial on the forum at
https://forum.openoffice.org/en/forum/viewtopic.php?f=74&t=12426#p58403 .
Regards
Keith
> Anyway, I'm going to place it into the /opt directory properly and use
> it. I'll report if there are any other problems.
>
> Thanks!!!
>
> Paul
>
>
>
>
>
>
> Openoffice_4.1
Re: Building OpenOffice on illumos with gcc
Posted by Paul Gress <pg...@optonline.net>.
On 08/ 6/14 02:01 AM, Alexander Pyhalov wrote:
> On 08/06/2014 02:37, Paul Gress wrote:
>> On 08/ 5/14 02:45 AM, Alexander Pyhalov wrote:
>>> On 08/01/2014 19:27, Alexander Pyhalov wrote:
>>>> Hello.
>>>> I've just integrated OpenOffice component into OpenIndiana /hipster
>>>> illumos distribution. I'd like to share some patches and to ask if they
>>>> could be converted to bug reports, feature requests and which of them
>>>> can be integrated.
>>>
>>> Could someone comment this?
>>>
>>
>>
>> Hi Alexander,
>>
>> I use Solaris 11.2. Is there a way to package this to install on 11.2?
>> Maybe tarred?
>
> http://buildzone.oi-build.r61.net/openoffice.tar.gz
>
> I'm not sure it will work on Solaris 11 as is.
>
>
Success, see below images. It appears to be functioning correctly as you can see there are no startup errors. Although I did notice one small nagging thing, the spell checker still doesn't work, as it stopped working also in 3.4. The last version it worked was in 3.3 compiled previously by Sun. Some people mentioned about Java labeling.
Anyway, I'm going to place it into the /opt directory properly and use it. I'll report if there are any other problems.
Thanks!!!
Paul
Openoffice_4.1
Re: Building OpenOffice on illumos with gcc
Posted by Alexander Pyhalov <al...@rsu.ru>.
On 08/06/2014 02:37, Paul Gress wrote:
> On 08/ 5/14 02:45 AM, Alexander Pyhalov wrote:
>> On 08/01/2014 19:27, Alexander Pyhalov wrote:
>>> Hello.
>>> I've just integrated OpenOffice component into OpenIndiana /hipster
>>> illumos distribution. I'd like to share some patches and to ask if they
>>> could be converted to bug reports, feature requests and which of them
>>> can be integrated.
>>
>> Could someone comment this?
>>
>
>
> Hi Alexander,
>
> I use Solaris 11.2. Is there a way to package this to install on 11.2?
> Maybe tarred?
http://buildzone.oi-build.r61.net/openoffice.tar.gz
I'm not sure it will work on Solaris 11 as is.
--
Best regards,
Alexander Pyhalov,
system administrator of Computer Center of Southern Federal University
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Building OpenOffice on illumos with gcc
Posted by Paul Gress <pg...@optonline.net>.
On 08/ 5/14 02:45 AM, Alexander Pyhalov wrote:
> On 08/01/2014 19:27, Alexander Pyhalov wrote:
>> Hello.
>> I've just integrated OpenOffice component into OpenIndiana /hipster
>> illumos distribution. I'd like to share some patches and to ask if they
>> could be converted to bug reports, feature requests and which of them
>> can be integrated.
>
> Could someone comment this?
>
Hi Alexander,
I use Solaris 11.2. Is there a way to package this to install on 11.2? Maybe tarred?
Thanks,
Paul
Re: Building OpenOffice on illumos with gcc
Posted by Alexander Pyhalov <al...@rsu.ru>.
On 08/01/2014 19:27, Alexander Pyhalov wrote:
> Hello.
> I've just integrated OpenOffice component into OpenIndiana /hipster
> illumos distribution. I'd like to share some patches and to ask if they
> could be converted to bug reports, feature requests and which of them
> can be integrated.
Could someone comment this?
--
Best regards,
Alexander Pyhalov,
system administrator of Computer Center of Southern Federal University
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: Building OpenOffice on illumos with gcc
Posted by Απόστολος Συρόπουλος <as...@hotmail.com>.
>
> We would need Apostolos to agree to contribute under the Apache
> License 2.0 as well, since this is based on his work. (Or did he
> already contribute the patches from his blog?) For example, it would
> be fine if he just sent a note to the mailing list, pointing to the
> blog posts, and saying that he contributes them to the AOO project
> under the Apache License 2.0.
>
Hello,
Of course I agree to include in the source tree anything you think is useful.
So please go ahead and include these patches.
Best regards,
Apostolos
--
Apostolos Syropoulos
Xanthi, Greece
Re: Building OpenOffice on illumos with gcc
Posted by Rob Weir <ro...@apache.org>.
On Fri, Aug 1, 2014 at 11:27 AM, Alexander Pyhalov <al...@rsu.ru> wrote:
> Hello.
> I've just integrated OpenOffice component into OpenIndiana /hipster illumos
> distribution. I'd like to share some patches and to ask if they could be
> converted to bug reports, feature requests and which of them can be
> integrated.
>
This is great news.
> OpenIndiana distribution tries to be compatible with Solaris 11. However,
> there are several distinctions, the main one is system compiler. We use gcc
> (4.8) with illumos (former Sun Solaris) linker instead of Sun Studio.
>
> The work I've made was based on earlier work of Apostolos Syropoulos, which
> he described here:
> https://asyropoulos.wordpress.com/2014/02/05/compiling-openoffice4/ .
>
We would need Apostolos to agree to contribute under the Apache
License 2.0 as well, since this is based on his work. (Or did he
already contribute the patches from his blog?) For example, it would
be fine if he just sent a note to the mailing list, pointing to the
blog posts, and saying that he contributes them to the AOO project
under the Apache License 2.0.
Thanks!
-Rob
> The full component is available here:
> https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openoffice/openoffice
> .
> And patches are in "patches" subdirectory:
> https://github.com/OpenIndiana/oi-userland/tree/oi/hipster/components/openoffice/openoffice/patches
> .
>
> I had to make about 20 changes.
>
> 01.use-illumos-ld.patch
> OpenOffice configure script doesn't like illumos ld and GCC on Solaris, so I
> relaxed this restriction.
>
> 02.use-gcc.patch
> Patches to main solenv/* make files are mostly taken from Apostolos blog
> (perhaps, with some corrections) and IIRC are based on Linux makefiles. They
> are necessary to introduce Solaris/GCC platform.
>
> 03.g++-includes.patch
> Our boost live in /usr/g++, so we have to teach OpenOffice to search it
> there. We can't use CPPFLAGS, because this breaks icu compilation. It would
> be perfect if we can provide boost path with configure switch.
>
> 04.gmake-j.patch
> dmake is supposed to call gmake in several cases. But sometimes it calls
> dmake or make and it doesn't like "-j" flags. Don't know why it happens. So
> I just had to remove "-j" flags.
>
> 05.visibility.patch
> Without this patch some symbols are hidden during sc compilation.
>
> 06.ignore_mapfiles.patch
> Some mapfiles introduce symbols which are not present in OpenIndiana.
>
> 07.cstring.patch
> Missing <cstring> includes.
>
> 08.adsyms.awk.patch
> Complements 06.ignore_mapfiles.patch. _ZTI* symbols are not present in
> result libraries.
>
> 09.libxmlsec-ldflags.patch
> LDFLAGS are not passed during libxmlsec build
>
> 10.xinerama.patch
> Two issues - 1) saldisp defines MAXFRAMEBUFFERS only for XSUN.
> 2) neither USE_XINERAMA_XORG nor USE_XINERAMA_XSUN are defined.
>
> 11.wmadaptor-gcc48.patch
> It seems just gcc 4.8 doesn't like &const_cast<char*>(pText) construction.
>
> 12.undefine-macroses.patch
> Some symbols used by OpenOffice are defined in our headers. Undefine them.
>
> 13.remove-studio-specific.patch
> Studio flags are unconditionally passed to the compiler. Fix this.
>
> 14.webdav-apr.patch
> On OpenIndiana we have /usr/apr/include, not /usr/include/apr. Also runpaths
> for APR and APR-UTIL are missing. Perhaps, adding some switch to set
> apr/apr-util runpath and include <header.h> instead of <apr/header.h> would
> help here.
>
> 15.icu.patch (in fact, patch to patch :))
> There are two issues.
>
> 1) in uperf.cpp _XOPEN_SOURCE_EXTENDED is defined. This hides some symbols
> on Solaris/illumos. So, we don't receive _XPG6 and get an error
> "Compiler or options invalid for pre-UNIX 03 X/Open applications \
> and pre-2001 POSIX applications"
> There's no need to define this guard on illumos.
>
> 2) We should add runpath to binaries, else compiling icu is linked to system
> icu in /usr/lib (compiled with Studio) and we receive binaries which are
> linked to both Studio and GCC C++ runtime simultaneously.
>
> 16.lstdc++.patch
> Binaries are unconditionally linked to lCstd on Solaris. Fix this.
>
> 17.nss.patch
> OpenOffice has hardcoded paths for nss libraries and headers. Set paths to
> our paths. One more time when having configure switch is desirable.
>
> 18.sal_osl_unx.patch
> 1) One more define supposing that the only Solaris compiler is Studio
> 2) We (as MACOSX) also have posix_madvise (just cut&paste Apostolos' change,
> don't know, why usual madvise fails to work, perhaps, missing headers).
>
> Post-install processing:
>
> bootstraprc has incorrect UserInstallation setting and tries to write user
> configs to installation directory (fix was taken from FreeBSD port). Alsoe
> some binaries have incorrect runpaths. Fix this.
>
> --
> Best regards,
> Alexander Pyhalov,
> system administrator of Computer Center of Southern Federal University
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org