Hello all, Things are not looking to good on the Debian / Ubuntu front for either WSPR or WSJT.
The suggested import call for python3-pil: from PIL.Image import core as _imaging seems to work on Debian Jessie and Ubuntu 14.10, but, both applications are failing with a Segfault on w.so for WSPR and Audio.so for WSJT. A guess as to why maybe related to gfortran v4.9x but that's purely a guess. At this point, I really cant do much more on Debian / Ubuntu until the Pillow and Segfault issues are resolved. Current Build Status as I know it to be: WSPR Debian: Jessie: fails Ubuntu: 14.04, Mint-17 seem ok. Ubuntu: 14.10: fails WSJT Debian: Wheezy (old version of WSJT), Jessie fails Ubuntu: 14.04, Mint-17 seem ok. Ubuntu: 14.10: fails 73's Greg, KI7MT On 01/06/2015 11:28 AM, ki7mt wrote: > Hello All, > > I did some testing on Windows last night. I was able to build and run > WSPR using Pillow v2.7.0 but, it required a minor import change to > wspr.py. The change did not fail when using Pillow v2.3.0. > > I found this today: > > Pillow >= 2.1.0 no longer supports “import _imaging”. Please use: > > “from PIL.Image import core as _imaging” instead. > > Link: http://pillow.readthedocs.org/en/latest/installation.html > > This directly relates to the: "import _imaging not found" error we're > seeing when using Pillow >=2.6.1. If 2.3.0, 2.6.1 and 2.7.0 all work as > expected when changing the import call to what the Pillow documents > state. Maybe a change in wsjt.py and wspr.py is in order?? > > On Windows, updating Pillow to 2.7.0 is easy using PIP3 and does not > require build / development dependencies, as it comes pre-built for the > Python version being used (3.3 / 3.4 etc). > > On Linux, however, it is not as simple. From my findings, most of the > ditro's that are using Pillow =< 2.5.0 compile against Tc\Tk-8.5-dev. > The distros using Pillow >= 2.6.1 are built against Tc\Tk-8.6-dev and > some additional image dependencies. > > Ubuntu 14.10 (Trusty) and Debian 8.0 (Jessie) are both using Pillow >> =2.6.1 built against Tc\Tk-8.6-dev. However, neither have yet to update > their python3-pil packages to 2.7.0. Is 2.6.1 really an issue? I don't > know. The question becomes, is it necessary to run 2.7.0 if the import > call is modified in WSJT.py and WSPR.py?? > > I've not had time to check Fedora, SUSE and neighboring RPM based > distro's, so if any of the RPM based package Maintainers could have a > poke around it would be most helpful. > > 73's > Greg, KI7MT > > -- ------------------------------------------------------------- The worth of man in reveled in his attitude to ordinary things when he is not before the footlights. (cf John 1:36) Oswald Chambers ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
