Eric, Yes, too eager...
I didn't get to the bottom part of the installation guide because I (almost) never use the J icons. I simply drop the j64-xxx distribution where (IMHO) it belongs (macOS /Applications, linux /usr/local/lib, Windows ... no idea... ) and set a symbolic link to jconsole in /usr/local/bin (both macOS and linux). I also copy my local profilex.ijs and personal_profile .ijs into the J/bin folder. Currently, in a terminal window, ja is J805 and jb is J806 this gave immediate satisfaction (after using pacman to install and update all the addons). When I did do all the steps (ignoring advice to put the J folder in my /User directory), things work as you suggest and pretty icons were generated on my Desktop (where I definitely don't want them!) The icons opened OK, but I put the jqt icon in my App Dock. Well, actually, it was the jqt806 icon - the previously defined jqt icon had lost it's link to the graphic for the icon (J replaced by ?) In any case, all that is just personal preferences and things do seem to work OK. I put the icons that were generated during the install into /Applications/j64-806/ (where I think they belong). Both before and after all this, the links that were in that directory in the distribution don't seem to work. They launch but noting happens except the following entries in /var/log/system.log Mar 12 13:34:28 MBpro com.apple.xpc.launchd[1] (com.apple.xpc.launchd.oneshot.0x10000033.apprun[8963]): Service exited with abnormal code: 127 Mar 12 13:34:28 MBpro com.apple.xpc.launchd[1] (com.apple.imfoundation.IMRemoteURLConnectionAgent): Unknown key for integer: _DirtyJetsamMemoryLimit Mar 12 13:34:28 --- last message repeated 1 time --- Mar 12 13:34:28 MBpro AssetCache[8972]: BUG in libdispatch: 16E183b - 3804 - 0x4 So if I tidy up, it may be to just delete the dysfunctional icons that came in the distribution. I know this is mostly noise since these things tend to be highly personal. But offered in the spirit of feedback. Thanks - joey > On 2017Mar 12, at 05:36, Eric Iverson <[email protected]> wrote: > > Ric, Joey, > > Thanks for the prompt feedback. > > You both report having to update addons before avx was defined. This is > because you guys took some shortcuts in the detail install steps. You went > to running avx in your first 806 session. Too eager! The install steps does > an update of all addons and creates launch icons. If you then stopped J and > restarted you would get the new installer with avx defined. > > > > On Sun, Mar 12, 2017 at 4:23 AM, Joey K Tuttle <[email protected]> wrote: > >> Seems not ... >> >> jkt@set1:~$ cat /proc/cpuinfo | grep avx >> jkt@set1:~$ >> >> No surprise, it's a few years old - >> >> jkt@set1:~$ cat /proc/cpuinfo >> processor : 0 >> vendor_id : GenuineIntel >> cpu family : 6 >> model : 30 >> model name : Intel(R) Xeon(R) CPU X3430 @ 2.40GHz >> >> But it would be good to have a more informative report from avx '' >> >> - joey >> >>> On 2017Mar 12, at 00:16, bill lam <[email protected]> wrote: >>> >>> You can first confirm if your linux box support avx or not, eg >>> >>> cat /proc/cpuinfo | grep avx >>> >> >> ---------------------------------------------------------------------- >> 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
