[SOLVED] openjdk from sbopkg won't build on current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
5. A number of Java Development Kits are suitable for building LibreOffice.
The default JDK for this SlackBuild is openjdk. Others may be chosen by
setting the JAVA environment variable when running the SlackBuild. Recognised
values are openjdk (the default, not explicitly required), openjdk8 and jdk
e.g. JAVA=jdk (to use SBo jdk package with Oracle binary version). Using an
alternate JDK will require presence of the appropriate package when building
LibreOffice. Since the apache-ant package is already required by openjdk,
hence openjdk8, its listing in the REQUIRES field is redundant in these cases.
However it remains listed to accomodate the case of JAVA=jdk, in which the
apache-ant package is needed to build LibreOffice.
Finally, setting JAVA=no will build LibreOffice without any Java support.
The simplest workaround at the moment is probably to use SBo's plain jdk (the Oracle binary repackaging) instead of openjdk.
Not true at all. In the case of libreoffice the simplest work around is to not build it with jdk support, its not required for most functionality. Personally I have never noticed any features missing from building libreoffice without jdk. The only required dependency for libreoffice on Slackware is perl-Archive-Zip. However you know this already and have simply disregarded it....
Not true at all. In the case of libreoffice the simplest work around is to not build it with jdk support, its not required for most functionality. Personally I have never noticed any features missing from building libreoffice without jdk. The only required dependency for libreoffice on Slackware is perl-Archive-Zip. However you know this already and have simply disregarded it....
The portion of the README previously quoted already mentions the possibility of building without a JDK. This is great feature of the SlackBuild system in general; that you can easily change any SlackBuild as you like to suit your particular needs.
However, for normal usage, I prefer SlackBuilds that by default produce functional packages rather than minimalist (simplistic?) packages.
chris
Last edited by chris.willing; 12-16-2017 at 08:12 PM.
However, for normal usage, I prefer SlackBuilds that by default produce functional packages rather than minimalist (simplistic?) packages.
chris
1. Libreoffice is perfectly functional without jdk.
2. Libreoffice is perfectly functional without avahi.
3. Libreoffice provides its own python3 implementation so that using the system python3 is entirely optional.
4. You are missing maybe a dozen + other optional dependencies that are available on SBo already.
I offered my libreoffice script to SBo a while before yours was accepted and it was rejected because they did not need two libreoffice scripts. Since this is no longer true I really do not appreciate that users keep tripping over your incomplete script you have refused to fix or that you managed to sneak your script in without anyone ever contacting me...
1. Libreoffice is perfectly functional without jdk.
2. Libreoffice is perfectly functional without avahi.
3. Libreoffice provides its own python3 implementation so that using the system python3 is entirely optional.
4. You are missing maybe a dozen + other optional dependencies that are available on SBo already.
I'm unsure of the point you're trying to make with this list - too many options included or not enough?
As already explained (or check the README), several user options determine inclusion (or not) of a particular JDK in the build.
Avahi is not included by default. As explained in the README, use "AVAHI=yes" if you want it included.
The python3 that LO can itself provide is sometimes not suitable, causing conflicts with any external applications trying to communicate with LibreOffice via the UNO bridge. Using a system python3 for both LibreOffice and the external application(s) prevents this problem. Perhaps this type of communication with external applications is not a feature that you personally use.
Quote:
Originally Posted by orbea
I offered my libreoffice script to SBo a while before yours was accepted and it was rejected because they did not need two libreoffice scripts. Since this is no longer true I really do not appreciate that users keep tripping over your incomplete script you have refused to fix or that you managed to sneak your script in without anyone ever contacting me...
I guess this is the real reason for the ongoing harping, across so many LibreOffice related threads, about options you don't agree with. I'm sorry you feel mistreated but assure you there was never any plot to "sneak" my script into SBo.
I built Libreoffice with JAVA=no and with "--with-system-poppler " removed from the slackbuild script. It worked great. I'm not sure what I might be missing without that option and without Java, but I'm not worried about it. Libreoffice is working properly and doing what I need it to do.
Thank you chris.willing for the slackbuild, and thank you AlleyTrotter for pointing out the option that needed to be remove when building with JAVA=no.
I'm marking this solved. I'm still curious about why gcc-java was removed from current, but I'm guessing it's been discussed in other threads and I can find it if I want.
I'm still curious about why gcc-java was removed from current, but I'm guessing it's been discussed in other threads and I can find it if I want.
Because gcc developers removed it with gcc7.
Quote:
As of GCC 7, the GCC Java frontend and associated libjava runtime library have been removed from GCC. The information on this page is kept here for reference but only applies to GCC 6 and earlier.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.