Hi Chuck, I did a bit of searching on RPM-FIND. for libfftwf3.a looks like you need:
For Static fftw-static For Dev Headers: fftw3-devel Share Libs fftw-libs-single-3.3.4-1 But I'm not an RPM expert. For me on Ubuntu 14.04, it was one package for all of them libfftw3-dev 73's Greg, KI7MT On 05/07/2014 03:28 PM, Chuck Forsberg WA7KGX wrote: > Turns out there is no libfftw3f.a on my system. > I downloaded the current fftw3 source from fftw.org, > compiled and installed it. Still no libfftw3f.a anywhere > on my system except for one in the wspr source > directory (??) > > On 05/07/2014 01:16 PM, Joe Taylor wrote: >> Chuck, Greg -- >> >>>> just now I installed python3-tkinter and now that compliant is gone. >> Yes. This is required, as stated before. >> >> >>>> Now "python3 wspr.py" stops complaining that >>>> >>>> [caf@omen3 wspr]$ python3 wspr.py >>>> Traceback (most recent call last): >>>> File "wspr.py", line 45, in<module> >>>> from WsprMod import w >>>> ImportError: /home/caf/wspr/WsprMod/w.so: undefined symbol: >>>> sfftw_destroy_plan_ >>>> [caf@omen3 wspr]$ >>> run: python3 -O wspr.py >>> >>> What's the results? >> Putting the "-O" into "python3 -O wspr.py" will have no effect on >> missing externals. >> >> Chuck: execute the following command in a terminal window: >> >> nm /your/path/to/libfftw3f.a | grep sfftw_destroy >> >> using whatever path leads to your installed libfftw3f.a. You should see >> something like >> >> 000001b0 T sfftw_destroy_plan_ >> 000014c0 T sfftw_destroy_plan__ >> >> If you don't, then your fedora installation does not have the required >> build of FFTW. You can build it yourself, or you can be patient and >> wait for us to (eventually) build it for you. >> >> -- 73, Joe, K1JT >> >> ------------------------------------------------------------------------------ >> Is your legacy SCM system holding you back? Join Perforce May 7 to find out: >> • 3 signs your SCM is hindering your productivity >> • Requirements for releasing software faster >> • Expert tips and advice for migrating your SCM now >> http://p.sf.net/sfu/perforce >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
