Re: [wsjt-devel] wspr 4 run problem

2014-05-13 Thread ki7mt
Hi Chuck, A quick glance at the Fedora Packaging Guidelines ( I believe that is the system your using, if not, this is mute) may shed some light on your anomalies: http://fedoraproject.org/wiki/Packaging:Guidelines In particular, section 1.10.6: http://fedoraproject.org/wiki/Packaging:Guideli

Re: [wsjt-devel] wspr 4 run problem

2014-05-13 Thread ki7mt
Hi Chuck, On 05/13/2014 04:17 PM, Chuck Forsberg WA7KGX wrote: > It is getting strange. I download a fresh wspr and then sh au*sh > then ./configure --libdir=/usr/lib64 > --with-portaudio-include-dir=/usr/include > --with-portaudio-lib-dir=/usr/lib64 > > Configure failed to choose f2py3 and did n

Re: [wsjt-devel] wspr 4 run problem

2014-05-13 Thread Chuck Forsberg WA7KGX
It is getting strange. I download a fresh wspr and then sh au*sh then ./configure --libdir=/usr/lib64 --with-portaudio-include-dir=/usr/include --with-portaudio-lib-dir=/usr/lib64 Configure failed to choose f2py3 and did not put anything into LIBS= I had to manually add -lportaudio -lfftw3f to

Re: [wsjt-devel] wspr 4 run problem

2014-05-13 Thread ki7mt
Hi Chuck, Thanks for the feedback. On 05/13/2014 05:47 AM, Chuck Forsberg WA7KGX wrote: > Python3 version 3.3.2 > f2py3 version 2 > f2py version 2 Cpython produces different outputs of w* based on the /usr/include/pythonx.xx. For example, on my Python3.4 system the output file is: w.cpython34

Re: [wsjt-devel] [PATCH] add 127.0.0.1:4532 to the port names for rigctld

2014-05-13 Thread Bill Somerville
On 13/05/2014 17:38, Rik van Riel wrote: Hi Rik, > On 05/13/2014 12:29 PM, Rik van Riel wrote: >> On 05/13/2014 12:24 PM, Bill Somerville wrote: >>> On 13/05/2014 17:13, Rik van Riel wrote: >>> Hi Rik, Hamlib NET rigctl listens on 127.0.0.1:4532 by default, so I had to add it in to the li

Re: [wsjt-devel] [PATCH] add 127.0.0.1:4532 to the port names for rigctld

2014-05-13 Thread Rik van Riel
On 05/13/2014 12:29 PM, Rik van Riel wrote: > On 05/13/2014 12:24 PM, Bill Somerville wrote: >> On 13/05/2014 17:13, Rik van Riel wrote: >> Hi Rik, >>> Hamlib NET rigctl listens on 127.0.0.1:4532 by default, so I had to add >>> it in to the list of port names allowed, in order for wsjtx to connect

Re: [wsjt-devel] [PATCH] add 127.0.0.1:4532 to the port names for rigctld

2014-05-13 Thread Bill Somerville
On 13/05/2014 17:29, Rik van Riel wrote: Hi Rik, > On 05/13/2014 12:24 PM, Bill Somerville wrote: >> On 13/05/2014 17:13, Rik van Riel wrote: >> Hi Rik, >>> Hamlib NET rigctl listens on 127.0.0.1:4532 by default, so I had to add >>> it in to the list of port names allowed, in order for wsjtx to con

Re: [wsjt-devel] [PATCH] add 127.0.0.1:4532 to the port names for rigctld

2014-05-13 Thread Rik van Riel
On 05/13/2014 12:24 PM, Bill Somerville wrote: > On 13/05/2014 17:13, Rik van Riel wrote: > Hi Rik, >> Hamlib NET rigctl listens on 127.0.0.1:4532 by default, so I had to add >> it in to the list of port names allowed, in order for wsjtx to connect >> to rigctld, and share the rig serial port with

Re: [wsjt-devel] [PATCH] add 127.0.0.1:4532 to the port names for rigctld

2014-05-13 Thread Bill Somerville
On 13/05/2014 17:13, Rik van Riel wrote: Hi Rik, > Hamlib NET rigctl listens on 127.0.0.1:4532 by default, so I had to add > it in to the list of port names allowed, in order for wsjtx to connect > to rigctld, and share the rig serial port with other programs. > > Ideally there would be an editable

[wsjt-devel] [PATCH] add 127.0.0.1:4532 to the port names for rigctld

2014-05-13 Thread Rik van Riel
Hamlib NET rigctl listens on 127.0.0.1:4532 by default, so I had to add it in to the list of port names allowed, in order for wsjtx to connect to rigctld, and share the rig serial port with other programs. Ideally there would be an editable field where the user can add any port name, but I have ne

Re: [wsjt-devel] wspr 4 run problem

2014-05-13 Thread Chuck Forsberg WA7KGX
Python3 version 3.3.2 f2py3 version 2 f2py version 2 MVSO:= ${MV} w.*.so WsprMod/w.so had to be changed to MVSO:= ${MV} w*.so WsprMod/w.so note: globbing != regex 4130 now recognizes f2py3 I added -lportaudio -lfftw3f to LIBS= and now wspr 4130 compiles and runs. On 05/13/2014 02:

Re: [wsjt-devel] wspr 4 run problem

2014-05-13 Thread ki7mt
Hi Chuck, I looked over potential causes for the issue you have. I found one thing that may be related, but a new checkout would have failed right at the beginning of make, so not sure that will resolve your problem. I still need the info from my previous post, in addition to that, could you t

Re: [wsjt-devel] wspr 4 run problem

2014-05-13 Thread ki7mt
Hi Chuck, Works fine on my box. What are you using? Did you do the install or try to run wspr.py from the source directory after build? When you say MVSO:= ${MV} w.*.so WsprMod/w.so doesnt' work, what is it *not* doing, copying the file, finding the file or not producing the file? What

[wsjt-devel] wspr 4 run problem

2014-05-13 Thread Chuck Forsberg WA7KGX
I get the following error when I compile and run wspr 4129 [caf@omen3 wspr]$ python3 -O wspr.py Traceback (most recent call last): File "wspr.py", line 45, in from WsprMod import w ImportError: dynamic module does not define init function (PyInit_w) Also the Makefile line MVSO: