For what it's worth, I now have jqt running on that laptop. Some issues I ran into:
(1) jqt requires libqt5websockets5, but this was not on the debian install media which I used. (Presumably because of space limitations, and the idea that it could be installed from the network.) Figuring out how to install this without a network connection with my current resources required some familiarity with the internal details of how debian manages packages. (First, I needed to locate a bullseye Packages.gz from a debian mirror and from that a libqt5websockets5_5.15.2-2_amd64.deb. Second I needed to install that using dpkg -i instead of apt install. I would have liked to use apt, but the windows version of jigdo was failing, and my previous experiences with memory consumption of ubuntu on windows even when it was not in use made me reluctant to install ubuntu on my small windows laptop.) (2) I was using /usr/bin/jqt (from the install-usr.sh) which in turn required a bunch of things installed to /usr/ which would "normally" be in a home directory: j903's bin/libj.so needed to go in /usr/bin/, and the the addons, system, and tools directories got copied directly into /usr/. Totally not ideal from a debian package management perspective... But, it works now. And, since I copied an entire set of addons from my windows J 903 instance, I also have a reasonably current set of addons on this machine. Next is to try compiling j here (windows j engine builds were running me into issues which I did not want to spend time on). FYI, -- Raul On Thu, Feb 17, 2022 at 7:10 PM Raul Miller <[email protected]> wrote: > > I'm installing j on a linux system. > > And, I ran into some issues with the j903/bin/install-usr.sh > > Specifically, if the system /bin/sh is not bash but some other sh > implementation, such as dash, running the script will give the > message: 'directory not j903' > > I believe the right fix for this would be to change the initial line to: > > #!/bin/bash > > Also, it assumes that it's being run with j903/bin as the current > directory. To make this more general, I think that before it executes > 'cd ..' it should execute: > > cd -P "$(dirname "$0")" > > Thanks, > > -- > Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
