Hi Randy, This thread is not a wsjt-devel list issue and should be taken off line.
I should clear up one point, PPA's are just personal package archives. What I was meaning by the preferred install method is by using the package manager rather than source building. I would start by reading through the following document, it's version states v2.0.19 but it's the same for v2.0.20. (Clicking the link will download the html file) https://sourceforge.net/projects/jtsdk/files/linux/2.0.0/documentation/release-notes/jtsdk-nix-2.0.19.html/download By adding the repository and installing with the package manager, updates arrive as they do for any other package rather than the user having to download and re-compile the application. Off hand, I do not know what version of Debian Raspian 8 is based on so I can't tell you how to add the repository properly. Your best off asking in the Raspian forums how to add Launchpad PPA's. 73's Greg, KI7MT On 05/13/2016 05:06 PM, Randy WB4SPB wrote: > OK, sorry to be redundant. I'm new to this and, although I've been > digging around for a week or so, I have run across no references to your > PPA -- don't know where to find it, don't actually know what a PPA is > (although I will now google it). When the .deb file I found at > http://physics.princeton.edu/pulsar/K1JT/wspr.html was unreadable by > dpkg on Rasbian, I used the most recent thing that was available at > https://sourceforge.net/projects/jtsdk/files/linux/2.0.0/. > > Where can I get v2.0.20-2 ? > > Randy WB4SPB > > On 5/13/2016 2:45 PM, Greg Beam wrote: >> Hi Randy, >> >> All of the issues your reporting below were resolved in my PPA >> (v2.0.20-2) some time ago, which is the preferred Debian / Ubuntu >> method of installation. >> >> 73's >> Greg, KI7MT >> >> On 05/13/2016 03:24 PM, Randy WB4SPB wrote: >>> Hi folks, >>> >>> In case you're interested, I have just built WSPR using jtsdk-nix-2.0.20 >>> on a Rpi running Rasbian 8.0 (Jessie). This was a fresh OS and jtsdk >>> install, and I ran into a few problems I had to work around. >>> >>> >>> 1) The jtsdk make failed because I was missing asciidoctor. I did: >>> >>> $ sudo gem install asciidoctor >>> >>> >>> 2) The jtsdk make complained because I was missing coderay. I did: >>> >>> $ sudo gem install coderay >>> >>> >>> 3) After a clean make, sudo make install failed as follows: >>> >>> ..Installing Manpages >>> install: cannot create regular file /usr/local/share/man/man1/jtsdk.1: >>> No such file or directory >>> Makefile:130: recipe for target 'install' failed >>> make: *** [install] Error 1 >>> >>> I edited Makefile to add: >>> >>> @$(MKDIR) $(DESTDIR)$(MANDIR) >>> >>> >>> 4) sudo make install failed as follows: >>> ..Changing /home/pi/jtsdk Ownership to: [ pi ] >>> /bin/chown: cannot access /home/pi/jtsdk: No such file or directory >>> Makefile:130: recipe for target 'install' failed >>> make: *** [install] Error 1 >>> >>> I edited Makefile to add: >>> >>> @$(MKDIR) $(HOMEDIR) >>> >>> >>> 5) After a successful install, I ran jtsdk and selected the WSPR menu >>> item. I saw: >>> >>> Checking Out New Version of wspr >>> svn: E175013: Unable to connect to a repository at URL >>> 'https://svn.code.sf.net/p/wspr/wspr/branches/wspr' >>> svn: E175013: Access to '/p/wspr/wspr/branches/wspr' forbidden >>> >>> >>> At http://physics.princeton.edu/pulsar/K1JT/devel.html I found a >>> different repository path, so I edited src/jtsdk-wspr as follows: >>> >>> $ diff jtsdk-wspr.orig jtsdk-wspr >>> 47c47 >>> < URL="https://svn.code.sf.net/p/wspr/wspr/branches/wspr"; >>> --- >>> > URL="https://svn.code.sf.net/p/wsjt/wsjt/branches/wspr"; >>> >>> Then after uninstall and reinstall, I was able to build WSPR. >>> >>> NOTE: there were some warnings... are warnings expected, or should I >>> try to document them? >>> >>> >>> I can now run WSPR on my Rpi, although the sound dongle I ordered has >>> not arrived yet so I can't get very far with it. >>> >>> >>> 73, >>> Randy WB4SPB >> = >> > ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
