Re: [wsjt-devel] JTSDK on ARM7hf

2016-01-11 Thread Bill Somerville
On 11/01/2016 12:44, Richard Bown wrote: > When all the settings below are greyed out , and empty, after leaving the > setting menu > you repeatedly get the message that the settings are incomplete. Hi Richard, it is probably saying that the settings are invalid. The most likely reason is that

Re: [wsjt-devel] JTSDK on ARM7hf

2016-01-11 Thread Bill Somerville
On 11/01/2016 09:41, Richard Bown wrote: > There is one minor problem, which I suspect has been picked up and dealt with. > In settings when rig is set to none , I keep getting the message that hamlib > is not set up. > When you test ptt again there is the hamlib error message straight away. >

Re: [wsjt-devel] JTSDK on ARM7hf

2016-01-10 Thread Greg Beam
Hi Richard, To make sure I understand where things stand, are you able to build Hamlib3, WSJTX and WSPR form the menus? I have an RPI2 that I can test with, so will do some testing when I have some spare time. >> > Hi Greg > WSJTX has been running now for a couple of hours , taking very

Re: [wsjt-devel] JTSDK on ARM7hf

2016-01-10 Thread Richard Bown
Hi all I pulled the latest trunk and built wsjt10 , it compiled without a hitch. on running I get:- odroid@odroid:~/wsjt10/trunk$ python3 -O wsjt.py Traceback (most recent call last): File "wsjt.py", line 9, in from WsjtMod import g, Audio ImportError:

Re: [wsjt-devel] JTSDK on ARM7hf

2016-01-10 Thread Richard Bown
On Sun, 10 Jan 2016 08:11:28 -0700 Greg Beam wrote: > Hi Richard, > > The PyCObject_Type error and the error your getting when trying to run > JTSDK ( the original problem you posted ) are two different things > completely. > > The PyCObject_Type error is almost certainly

Re: [wsjt-devel] JTSDK on ARM7hf

2016-01-10 Thread Greg Beam
Hi Richard, OK, thanks. What changes were made to the Makefile? I am assuming the WSJT Makefile is what's being modified here. JTSDK does not set nor check for OS subs, the Unsupported OS message must be coming from the WSJT 10 configure.ac / Makefile. I'll look at this later this afternoon.

Re: [wsjt-devel] JTSDK on ARM7hf

2016-01-10 Thread Greg Beam
Hi Richard, The PyCObject_Type error and the error your getting when trying to run JTSDK ( the original problem you posted ) are two different things completely. The PyCObject_Type error is almost certainly due to the fact when you manually built WSJT-10, the build used Python2-Numpy and not

Re: [wsjt-devel] JTSDK on ARM7hf

2016-01-10 Thread Richard Bown
On Sun, 10 Jan 2016 15:44:53 + Richard Bown wrote: > On Sun, 10 Jan 2016 08:11:28 -0700 > Greg Beam wrote: > > > Hi Richard, > > > > The PyCObject_Type error and the error your getting when trying to run > > JTSDK ( the original problem you posted )

Re: [wsjt-devel] JTSDK on ARM7hf

2016-01-10 Thread Richard Bown
On Sun, 10 Jan 2016 11:02:46 -0700 Greg Beam wrote: > Hi Richard, > > OK, thanks. What changes were made to the Makefile? I am assuming the > WSJT Makefile is what's being modified here. > > JTSDK does not set nor check for OS subs, the Unsupported OS message > must be

Re: [wsjt-devel] JTSDK on ARM7hf

2016-01-10 Thread Greg Beam
Hi Richard, Ok, that's making more sense now. The Linux WSJT Makefile has not been updated similar to WSPR to find Python3 and it's associated F2PY. I was mistaken on the Unsupported OS error message, that *is* coming frrm the JTSDK WSJT build script. I can fix that easily enough, but that

Re: [wsjt-devel] JTSDK on ARM7hf

2016-01-10 Thread Richard Bown
On Sun, 10 Jan 2016 11:48:00 -0700 Greg Beam wrote: > Hi Richard, > > Ok, that's making more sense now. The Linux WSJT Makefile has not been > updated similar to WSPR to find Python3 and it's associated F2PY. > > I was mistaken on the Unsupported OS error message, that *is*