Nice/easier way to go for an update - but ... I was flummoxed for awhile by -
'update' jpkg 'all'
Updating server catalog...
Local JAL information was last updated: 14 Jan 2019 09:08:52
Installed addons are up to date, 1 addon are not yet installed.
There is a newer version of the base library.
Actually I tried several times and different ways and ... but always got that
there was a newer version waiting.
Finally, I decided to blunder ahead, restart J and do (as instructed) -
load 'pacman'
je_update_jpacman_'' NB. download latest JE
http://www.jsoftware.com/download/jengine/j807-release/linux/j64/libj-nonavx.so
saved as: ~temp/je_update/libj.so.new
new version:
j807/j64nonavx/linux/release-a/commercial/www.jsoftware.com/2019-01-11T11:06:44
hint: copy command so you can paste it in terminal/command window
!!! shutdown J (all copies running this version) !!!
in a terminal/command window run the following:
"/home/jkt/Documents/jstuff/j64-807-user/temp/je_update/update.sh"
note: command may require admin/sudo priviliege
and even though the path for the installation was not where my normal system
resides, copying an pasting the update.sh line did in fact do the right thing -
and when I
jkt@set1:~$ sudo
/home/jkt/Documents/jstuff/j64-807-user/temp/je_update/update.sh
[sudo] password for jkt:
restart J and check JVERSION
jkt@set1:~$ ja
JVERSION
Engine: j807/j64nonavx/linux
Release-a: commercial/2019-01-11T11:06:44
Library: 8.07.22
Platform: Linux 64
Installer: J807 install
InstallPath: /usr/local/lib/j64-807
Contact: www.jsoftware.com
load 'pacman'
'update' jpkg ''
Updating server catalog...
Local JAL information was last updated: 14 Jan 2019 09:39:15
Installed addons are up to date, 1 addon are not yet installed.
The base library is up to date.
JVERSION
Engine: j807/j64nonavx/linux
Release-a: commercial/2019-01-11T11:06:44
Library: 8.07.22
Platform: Linux 64
Installer: J807 install
InstallPath: /usr/local/lib/j64-807
Contact: www.jsoftware.com
then, looking at my environment -
jkt@set1:~$ ls -lRrt Documents/jstuff/j64-807-user/
Documents/jstuff/j64-807-user/:
total 20
drwxrwxr-x 2 jkt jkt 4096 Jun 7 2018 snap
drwxrwxr-x 2 jkt jkt 4096 Jun 7 2018 projects
drwxrwxr-x 2 jkt jkt 4096 Jun 7 2018 config
drwxrwxr-x 3 jkt jkt 4096 Jan 14 09:39 temp
drwxrwxr-x 2 jkt jkt 4096 Jan 14 09:43 break
Documents/jstuff/j64-807-user/snap:
total 0
Documents/jstuff/j64-807-user/projects:
total 0
Documents/jstuff/j64-807-user/config:
total 0
Documents/jstuff/j64-807-user/temp:
total 2880
-rw-rw-r-- 1 jkt jkt 94697 Sep 19 12:15 plot.pdf
-rw-rw-r-- 1 jkt jkt 2839960 Jan 11 08:15 libj-nonavx.so
drwxrwxr-x 2 jkt jkt 4096 Jan 14 09:35 je_update
Documents/jstuff/j64-807-user/temp/je_update:
total 5556
-rw-rw-r-- 1 jkt jkt 2840040 Jan 14 09:35 libj.so.old
-rw-rw-r-- 1 jkt jkt 2839960 Jan 14 09:35 libj.so.new
-rwxrwxr-x 1 jkt jkt 153 Jan 14 09:35 update.sh
Documents/jstuff/j64-807-user/break:
total 8
-rw-rw-r-- 1 jkt jkt 1 Oct 29 20:59 8473.default
-rw-rw-r-- 1 jkt jkt 1 Jan 14 09:34 18095.default
jkt@set1:~$ ls -lrt /usr/local/lib/j64-807/
total 32
then, puzzling over why it worked and used my /usr/local/bin/ links, looking at
the normal home (/usr/local/lib) I was pleased to see -
jkt@set1:~$ ls -lrt /usr/local/lib/j64-807/bin
total 2848
-rw-r--r-- 1 jkt jkt 904 Dec 21 2016 profilex.ijs
-rw-r--r-- 1 jkt jkt 27392 Aug 8 16:51 quedprof.ijs
-rw-rw-r-- 1 jkt jkt 818 Oct 5 13:36 profilex_template.ijs
-rw-rw-r-- 1 jkt jkt 1878 Oct 5 13:36 profile.ijs
-rwxr-xr-x 1 jkt jkt 143 Oct 5 13:36 jhs
-rwxr-xr-x 1 jkt jkt 16376 Oct 5 13:36 jconsole
-rwxr-xr-x 1 jkt jkt 56 Oct 5 13:36 jbrk
-rw-rw-r-- 1 jkt jkt 13 Oct 5 13:36 installer.txt
drwxr-xr-x 2 jkt jkt 4096 Oct 5 13:36 icons
-rwxr-xr-x 1 jkt jkt 2839960 Jan 14 09:38 libj.so
jkt@set1:~$
So, things were done very nicely, even keeping a backup copy of the previous
version of JE. The only confusing part was right at the start.
Moving on to my Mac OS 10.14.3 environment. The same things happened, but this
time I didn't keep repeating step one, just blundered ahead to success.
Thanks for the updates - and the improvements keep coming. Looking at my
infamous/ancient benchmark -
JVERSION
Engine: j807/j64/darwin
Release-a: commercial/2019-01-11T11:43:43
Library: 8.07.22
Platform: Darwin 64
Installer: J807 install
InstallPath: /applications/j64-807
Contact: www.jsoftware.com
timex '%. 1000 1000 ?@$ 0'
0.502563 69208384
and comparing it to J805
JVERSION
Engine: j805/j64/darwin
Release: commercial/2016-12-11T08:17:56
Library: 8.05.10
Platform: Darwin 64
Installer: J805 install
InstallPath: /applications/j64-805
Contact: www.jsoftware.com
1.951981 69209088
1.951981 69209088 % 0.502563 69208384
3.884052348 1.000010172
I continue to be amazed/impressed that there is almost a 4x speedup (and takes
less memory) - NICE!
- joey
> On 2019Jan 14, at 05:49, Eric Iverson <[email protected]> wrote:
>
> J807 was released 2018 Oct 8. Since then a few bugs have been reported in
> JE (J Engine) shared library. They have been fixed and it is time for a
> maintenance release.
>
> Release packages (zip and aio) have been built with the new JE and are now
> available.
>
> New version info (JVERSION and 9!:14'') is release-a.
>
> New installs will get release-a.
>
> You can get release-a without having to do a complete new install (as would
> have been required in previous releases).
>
> If you are running j807 and want to upgrade to release-a, do the following:
>
> ***
> start J
> run pacman and get latest base library
> restart J with latest base library
>
> load'pacman'
> je_update_jpacman_'' NB. download latest JE
> ... instructions ...
>
> The instructions are to shutdown J and run a shell script (bat or sh file)
> to replace the old binary with the new.
> ***
>
> See:
> https://code.jsoftware.com/wiki/System/ReleaseNotes/J807
> for release info.
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
