rhino build failed when rhino 1.7r5 is used in OpenJDK

2015-05-07 Thread Alexander Pyhalov

Hello.
After updating rhino used by OpenJDK to rhino1_7R5  I can't longer 
compile openoffice, because rhino build fails. Does someone has any cure 
for this? Rhino build output follows.


Entering 
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino


mkdir: Failed to make directory unxsogi.pro/misc/build/rhino1_7R3/; 
File exists
Buildfile: 
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/build.xml


properties:

init:

compile:

compile-most:

compile-jdk15:

compile:

properties:

compile:

xmlimplsrc-compile:
 [echo] Calling 
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/xmlimplsrc/build.xml


compile:

e4x-compile:
[javac] Compiling 8 source files to 
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/build/classes
[javac] warning: [options] bootstrap class path not set in 
conjunction with -source 1.5
[javac] 
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/xmlimplsrc/org/mozilla/javascript/xmlimpl/XMLObjectImpl.java:271: 
error: method does not override or implement a method from a supertype

[javac] @Override
[javac] ^
[javac] 
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/xmlimplsrc/org/mozilla/javascript/xmlimpl/XMLObjectImpl.java:286: 
error: method does not override or implement a method from a supertype

[javac] @Override
[javac] ^
[javac] 
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/xmlimplsrc/org/mozilla/javascript/xmlimpl/XMLObjectImpl.java:305: 
error: method does not override or implement a method from a supertype

[javac] @Override
[javac] ^
[javac] 
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/xmlimplsrc/org/mozilla/javascript/xmlimpl/XMLObjectImpl.java:321: 
error: method does not override or implement a method from a supertype

[javac] @Override
[javac] ^
[javac] 
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/xmlimplsrc/org/mozilla/javascript/xmlimpl/XML.java:47: 
error: XML is not abstract and does not override abstract method 
getFunctionProperty(Context,int) in XMLObject

[javac] class XML extends XMLObjectImpl {
[javac] ^
[javac] 
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/xmlimplsrc/org/mozilla/javascript/xmlimpl/XMLList.java:48: 
error: XMLList is not abstract and does not override abstract method 
getFunctionProperty(Context,int) in XMLObject

[javac] class XMLList extends XMLObjectImpl implements Function {
[javac] ^
[javac] 6 errors
[javac] 1 warning

BUILD FAILED
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/build.xml:77: 
The following error occurred while executing this line:
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/build.xml:108: 
The following error occurred while executing this line:
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/xmlimplsrc/build.xml:60: 
The following error occurred while executing this line:
/export/home/alp/srcs/oi-userland/components/openoffice/openoffice/build/i86/main/rhino/unxsogi.pro/misc/build/rhino1_7R3/xmlimplsrc/build.xml:77: 
Compile failed; see the compiler error output for details.




--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Can't create new ODF files

2014-10-06 Thread Alexander Pyhalov
 related. Does someone have any hints how to debug 
this issue?


--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Building OpenOffice on illumos with gcc

2014-08-06 Thread Alexander Pyhalov

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-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Building OpenOffice on illumos with gcc

2014-08-06 Thread Alexander Pyhalov



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-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Building OpenOffice on illumos with gcc

2014-08-06 Thread Alexander Pyhalov

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-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Building OpenOffice on illumos with gcc

2014-08-06 Thread Alexander Pyhalov

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-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Re: Building OpenOffice on illumos with gcc

2014-08-05 Thread Alexander Pyhalov

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-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



Building OpenOffice on illumos with gcc

2014-08-01 Thread Alexander Pyhalov

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_castchar*(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 cutpaste 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-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org