Does anybody have a SlackBuild for Libre Office (ARM).
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
It would be possible to build OpenJDK on Slackware ARM 13.37 ... I did the same for Slackware 13.37. But you have to tweak the installation of gcc and seamonkey for that.
There are two scripts which I wrote that apply these tweaks. They are in my openjdk/build directory: create_gcj_jvm.sh
and fix_seamonkey_pkgconfig.sh. Run both of them, once. The change will be permanent for gcc (basically it will add a directory structure with a lot of symlinks and this will not alter any of the existing gcc files). The change willnot be permanent for seamonkey: it will be undone when you upgrade that package.
After running those two scripts, try compiling openjdk again. And remove any old Sun/Oracle JDK/JRE first! And logout/login again.
checking for a JDK home directory... /usr/lib/jvm
checking if a java binary was specified... no
checking if /usr/lib/jvm/bin/java is a valid executable file... yes
checking for javac... /usr/lib/jvm/bin/javac
checking for ecj... /usr/bin/ecj
checking if we are using ecj as javac... yes
checking if a javah executable is specified... no
checking if /usr/lib/jvm/bin/javah is a valid executable file... yes
checking if a jar executable is specified... no
checking if /usr/lib/jvm/bin/jar is a valid executable file... yes
checking whether jar supports @<file> argument... yes
checking whether jar supports stdin file arguments... yes
checking whether jar supports -J options at the end... yes
checking if an rmic executable is specified... no
checking if /usr/lib/jvm/bin/rmic is a valid executable file... yes
checking if a native2ascii binary was specified... no
checking if /usr/lib/jvm/bin/native2ascii is a valid executable file... no
checking for native2ascii... no
checking for gnative2ascii... no
configure: error: "A native2ascii converter was not found."
make: *** No targets specified and no makefile found. Stop.
Ah yes, this is a bug in the packaging of the gcc compilers, which was fixed in Slackware-current.
The gnative2ascii program is mistakenly present in the gcc-gnat package. Install that and try again.
Better even: do a full Slackware install and then try again. I usually do not support failed compilations on non-full Slackware installations.
I uploaded my LibreOffice 3.5.2 packages earlier today. The SlackBuild I used for those, is the same which is compiling LibreOffice on my trimslice at the moment (going at it for a day already): http://slackware.com/~alien/slackbui...ice.SlackBuild . Note that the build directory contains two patches specific to ARM and gcc 4.7. Let's hope the build succeeds before the trimslice runs out of diskspace... like it did yesterday.
Needless to say that I am building on a slackware-current port for ARM. It needs Java and gcj will not do. You will need OpenJDK which I could only compile on -current for ARM (needed a recent gcc and glibc).