Add support for document server on OpenPOWER/Linux systems

[madscientist159]

Tested with Debian Buster and GCC 6
GCC 8 is known not to work due to architecture-independent problems in the old version of v8 used by ONLYOFFICE

This partially resolves #859

[ShockwaveNN]

@K0R0L @agolybev please take a look at this PR

[ShockwaveNN]

@madscientist159 Any advice how to setup VM to emulate openPOWER?

[madscientist159]

Any advice how to setup VM to emulate openPOWER?

qemu-system-ppc64 -machine pseries -cpu power9 -nodefaults -nographic -serial stdio

Note this can be painfully slow -- if you need to do any significant work on POWER you can get a small VPS over at https://www.integricloud.com , otherwise if there's a desire to have actual CI / ppc64le builds there is a possibility we could provide free access to a dedicated VM for that work.

[madscientist159]

Just wondering if there was any progress toward merge? We've been using an instance based on this on POWER ever since the patch was created, no platform-specific issues, works very well.

[ShockwaveNN]

@madscientist159 Sorry. No news, trying to get access to OpenPOWER server to try compilation on my own, but currently stuck with our internal issues about paying for account

[ShockwaveNN]

Just a minor news - we bought access to integricloud servers and now I'm trying to setup one. Seems this is not as easy task as start cloud instance in amazon, so as soon as were will be real progress - I leave a message here

[ShockwaveNN]

Ok, I finally run debian 10 on ppc64le

Started script with
cd ~/build_tools/tools/linux/ && python3 ./automate.py

And got error with

bash: ./node_js_setup_10.x: No such file or directory

And I don't see any changes in your script to nodejs except just not install it

But our product will not work with nodejs

[krosseyed]

It looks like everything compiles and node + python are working as intended. The automate.py script downloads version 10.19.0 of nodejs

However, when running the automate.py script I get an error about cef_binary.7z not being an archive file.

I am running Ubuntu Server 20.04 LTS on Kernel 4.15.0-106 ppc64le

I can reproduce this by running the following script:

https://gist.github.com/krosseyed/1a2b203776636c8a4736e00a7b41a6e7

Error Output:

7-Zip 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
p7zip Version 16.02 (locale=C.UTF-8,Utf16=on,HugeFiles=on,64 bits,72 CPUs LE)

Scanning the drive for archives:
1 file, 302 bytes (1 KiB)

Extracting archive: ./cef_binary.7z
ERROR: ./cef_binary.7z
./cef_binary.7z
Open ERROR: Can not open the file as [7z] archive


ERRORS:
Is not archive
    
Can't open as archive: 1
Files: 0
Size:       0
Compressed: 0
Error (7z): 2
Error (./make.py): 1

[ShockwaveNN]

Error with cef_binary is because we download cef from our s3 bucket

build_tools/scripts/core_common/modules/cef.py

Line 18 in 552be8d

url = "http://d2ettrnqo7v976.cloudfront.net/cef/3770/"

And there is no variant for ppc64le

[madscientist159]

CEF is not needed for the server version. If I recall correctly I just commented the CEF fetch part of the script out and made sure not to build the client version.

[CLAassistant]

All committers have signed the CLA.

[madscientist159]

Updated and verified to work in conjunction with ONLYOFFICE/core#904

[madscientist159]

Just a friendly ping on this. How can we get this merged? At this point it's deployed in production on OpenPOWER at a number of organizations and maintained by Raptor, we even have CI/CD here:

https://gitlab.raptorengineering.com/raptor-engineering-public/onlyoffice/build_tools/