No. I reset libj.so to the j805 version and left jconsole at the j804 version and got this:

[dm@centos6-64 j64-805]$ ./jconsole
Load library /home/dm/Downloads/j64-805/bin/libj.so failed.
[dm@centos6-64 j64-805]$ ldd libj.so
./libj.so: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by 
./libj.so)

On 12/21/2016 06:52, bill lam wrote:
does libj.so from j805 work?

On 21 Dec, 2016 7:17 pm, "David Mitchell" <[email protected]> wrote:

Eric,

I copied over jconsole and libj.so from j64-804/bin to j64-805.bin.

I was able to run jconsole, jhs (including a complete JAL install) and
updatejqt.sh without errors.

 J Http Server
Engine: j804/j64/linux
Release: commercial/2015-12-28 10:47:03
Library: 8.05.10
Platform: Linux 64
Installer: J805 install
InstallPath: /home/dm/Downloads/j64-805
Contact: www.jsoftware.com

Copyright 1994-2016 Jsoftware Inc.

jqt failed, as Bill suspected, with a qt5 issue:

[dm@centos6-64 j64-805]$ ./jqt.sh
bin/jqt: error while loading shared libraries: libQt5Gui.so.5: cannot open
shared object file: No such file or directory

[dm@centos6-64 j64-805]$ ldd bin/jqt
        linux-vdso.so.1 =>  (0x00007ffd2b7df000)
        libQt5Gui.so.5 => not found
        libQt5Core.so.5 => not found

[dm@centos6-64 j64-805]$ sudo yum list installed | grep -i qt5
qt5-qtbase.i686         5.6.1-3.el6     @epel
qt5-qtbase-common.noarch
qt5-qtbase-gui.i686     5.6.1-3.el6     @epel

[dm@centos6-64 j64-805]$ sudo yum provides libQt5Gui.so.5
qt5-qtbase-gui-5.6.1-3.el6.i686 : Qt5 GUI-related libraries
Repo        : installed
Matched from:
Other       : Provides-match: libQt5Gui.so.5

On 12/19/2016 09:35, Eric Iverson wrote:

David,
If possible, please confirm that the 804 jconsole lets you run the latest
805 JE. That is, that installing 805 and then replacing jconsole with the
804 jconsole gives you a fully functioning 805 system.

If you can confirm, we will provide support and steps for this in the 805
release install steps.

On Sun, Dec 18, 2016 at 8:04 PM, David Mitchell <[email protected]>
wrote:

I agree, in general.  I do not have an immediate concern related to this
situation.

I just wanted to report it, since Centos 6 is likely to remain a
supported
OS until December 2020.

The issue and workarounds may be worth noting in the release notes of
j805.


On 12/18/2016 19:23, Eric Iverson wrote:

Bill has perhaps already suggested an adequate workaround. We need to
pick
a particular version for our builds. We try to not be too far behind, or
too recent.

You could also build a jconsole for you centos 6 platform from the
source.

These workarounds are probably preferable to the 'upgrade your system'
solution.

Unless this shows up as a problem for lots of users we are unlikely to
build an alternative version or build for the older systems.

On Sun, Dec 18, 2016 at 2:41 PM, David Mitchell <[email protected]>
wrote:

I get this error with j805 jconsole on Centos 6:


./jconsole: /lib64/libc.so.6: version `GLIBC_2.14' not found (required
by
./jconsole)

My install of Centos 6 has glibc 2.12.

My Centos 7 does not have this problem.

David Mitchell
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

----------------------------------------------------------------------

For information about J forums see http://www.jsoftware.com/forums.htm

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to