[Slackbuilds-users] dbeaver-ce not finding jre

Dave Woodfall dave at slackbuilds.org
Fri Jun 19 20:29:41 UTC 2020


On 19/06/20 12:34,
Rich Shepard <rshepard at appl-ecosys.com> put forth the proposition:
> Here there is no /usr/lib64/java. I have JAVA_HOME=/usr/lib64/jvm/bin/java.

But you set that yourself, yes?

ls $JAVA_HOME/
bin/   include/  lib/  sample/             LICENSE             release
demo/  jre/      man/  ASSEMBLY_EXCEPTION  THIRD_PARTY_README  src.zip

It's the ROOT or HOME directory of where java things are found, but
What you have set is the path to only the java BINARY.

(Your listing may be slightly different, but it should have similar
directories and files.)

> I must have mis-understood what B. wrote when he said the second path was
> where java was to be found.

Regardless, when you install the package it will drop a file in
/etc/profile.d/ which sets these things up for you automatically.

Unless you are doing something unusual, all you need to do is install
the package, logout, login, and JAVA_HOME will be set.

If you are installing the package as part of a list of packages, then
you may need to pause the queue and do this before installing the rest
of the list.  Making jdk (or openjdk) first in the list is probably a
good idea to make things easier.

Please remove or comment out the line(s) in your ~/.bash_profile and
logout and in again.  If you have set it in both root's and your
user's ~/.bash_profile then edit both of them.

You may also need to log out of X and its controlling tty too, if
started with startx.  If you're using a session manager to login,
then doing a ctrl-alt-backspace usually works.  If all this seems
like it's getting too complicated then rebooting is sometimes easier.

(That applies to everything that drops an executable .sh file in
/etc/profile.d/, not just for java.)

After that, check what `ls $JAVA_HOME' shows.

> Which of the many jdks in the SBo repo are you running, Dave? I've no
> preference as long as one version works.

Since it's usually installed as a package listed in REQUIRES in the
.info file, you should usually go by what is listed in that.

Having said that, openjdk has the advantage over jdk that the tarball
can be downloaded without needing to go to the java website and
downloading it manually.  Using the latest openjdk is a good choice
IMHO.

I haven't found anything that wouldn't build with openjdk and
required the jdk from Solaris for some years (although it was
developed by Sun then) but YMMV.

--
Dave
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20200619/c5a7f764/attachment.asc>


More information about the SlackBuilds-users mailing list