[Alug]Spell checking greyed-out in Sylpheed-Claws
Hi folks, I have just installed sylpheed-claws 0.8.11 on my PC but the "spelling" option is greyed out in the compose window. If I type "which aspell" (or ispell) my system confirms that they are installed in /usr/bin so I am not sure why the spell checking function is not available within Sylpheed. Does anyone have any ideas about what I need to tweak in order to get this function working? Ian.
main-admin@lists.alug.org.uk wrote on 20 April 2003 08:50:
I have just installed sylpheed-claws 0.8.11 on my PC but the "spelling" option is greyed out in the compose window. If I type "which aspell" (or ispell) my system confirms that they are installed in /usr/bin so I am not sure why the spell checking function is not available within Sylpheed. Does anyone have any ideas about what I need to tweak in order to get this function working?
If you've installed Sylpheed via tarball, you'll need to explicity tell it to use aspell/ispell at configure time. Type ./configure --help for the list of options. Regards, Martyn -- Affordable web hosting packages from Martyn Drake -> http://forum.movielad.co.uk/viewforum.php?f=2
On Sunday 20 April 2003 9:55 am, Martyn Drake wrote:
If you've installed Sylpheed via tarball, you'll need to explicity tell it to use aspell/ispell at configure time. Type ./configure --help for the list of options.
Thanks for the tip Martyn. The tarball I have downloaded is: -rw-r--r-- 1 root root 2647125 Apr 18 18:06 sylpheed-0.8.11claws.tar.gz which I unpacked. I have had a look at the ./configure --help and notice these options which may be relevant: --enable-aspell Enable GNU/aspell support default=no --with-aspell-prefix=PFX Prefix where aspell is installed (optional) --with-aspell-libs=LIBS Where GNU/aspell library reside (/usr/local/lib) --with-aspell-includes=INCLUDES Where GNU/aspell headers reside (/usr/local/include) I have had a look in /usr/local/lib (where sylpheed expects to find the libs?) and can see: bash-2.05a$ ls /usr/local/lib X11 libaspell.so.15 libpspell.so libaspell.la libaspell.so.15.0.2 libpspell.so.15 libaspell.so libpspell.la libpspell.so.15.0.2 and if I look in /usr/local/include (where sylpheed expects to find the includes?) I can see: bash-2.05a$ ls /usr/local/include aspell.h pspell I therefore assume that these default locations are correct so tried just: ./configure --enable-aspell Amongst all the messages which scrolled past I could see: checking whether to use GNU/aspell... yes checking for aspell... /usr/local/bin/aspell checking for GNU/aspell - version >= 0.50... yes checking for GNU/aspell dictionaries location... /usr/local/lib/aspell checking if GNU/aspell is correctly installed... no *** The GNU/aspell test program did not succeed. This usually means that *** the headers and the libraries could not be found. Check config.log *** for detailed error message and add the relevant options *** --with-aspell-prefix, --with-aspell-includes or --with-aspell-libs *** to the configure command. *** This can also mean that the library was not found at runtime. In that case *** add its path to LD_LIBRARY_PATH environment variable or in /etc/ld.so.conf This suggests I look at config.log. If I look in that, then, amongst all the information I see a section which says: configure:16043: checking for aspell configure:16061: found /usr/local/bin/aspell configure:16074: result: /usr/local/bin/aspell configure:16082: checking for GNU/aspell - version >= 0.50 configure:16127: gcc -o conftest -g -O2 conftest.c >&5 configure:16130: $? = 0 configure:16132: ./conftest configure:16135: $? = 0 configure:16150: result: yes configure:16152: checking for GNU/aspell dictionaries location configure:16160: result: /usr/local/lib/aspell configure:16162: checking if GNU/aspell is correctly installed configure:16197: gcc -o conftest -g -O2 -I/usr/local/include conftest.c -L/us r/local/lib -laspell >&5 configure:16200: $? = 0 configure:16202: ./conftest ./conftest: error while loading shared libraries: libaspell.so.15: cannot open shared object file: No such file or directory configure:16205: $? = 127 configure: program exited with status 127 Unfortunately I don't know much about installing programs via tarballs and was wondering if someone could interpret the above messages for so so I can suss out what I need to do to get sylpheed-claws to compile with a spell checker. Thanks, Ian. PS: Operating Sytem = Slackware 8.2 if this is relevant.
On Sun, 20 Apr 2003 13:31:15 +0100 Ian Douglas <alug@k1ngph1cher.com> wrote:
bash-2.05a$ ls /usr/local/lib X11 libaspell.so.15 libpspell.so libaspell.la libaspell.so.15.0.2 libpspell.so.15 libaspell.so libpspell.la libpspell.so.15.0.2
then...
configure:16202: ./conftest ./conftest: error while loading shared libraries: libaspell.so.15: cannot open shared object file: No such file or directory configure:16205: $? = 127 configure: program exited with status 127
I looks like the program is trying to load the shared library by using the name libaspell.so.15 whereas the library is probably actually in the file libaspell.so.15.0.2 libaspell.so.15 should be a symbolic link to libaspell.so.15.0.2 - if it isn't then this is probably the problem - you just need to remove libaspell.so.15 and re-link it. Steve.
On Sunday, April 20, 2003 5:04 PM, Steve Fosdick wrote:
Ian Douglas wrote:
bash-2.05a$ ls /usr/local/lib X11 libaspell.so.15 libpspell.so libaspell.la libaspell.so.15.0.2 libpspell.so.15 libaspell.so libpspell.la libpspell.so.15.0.2
then...
configure:16202: ./conftest ./conftest: error while loading shared libraries: libaspell.so.15: cannot open shared object file: No such file or directory configure:16205: $? = 127 configure: program exited with status 127
I looks like the program is trying to load the shared library by using the name libaspell.so.15 whereas the library is probably actually in the file libaspell.so.15.0.2 libaspell.so.15 should be a symbolic link to libaspell.so.15.0.2 - if it isn't then this is probably the problem - you just need to remove libaspell.so.15 and re-link it.
Thanks for the tip Steve. However, unfortunately, it looks like the file is already linked: bash-2.05a$ ls -l /usr/local/lib total 7884 drwxr-xr-x 3 root root 4096 Apr 18 16:22 X11 -rwxr-xr-x 1 root root 809 Apr 20 12:34 libaspell.la lrwxrwxrwx 1 root root 19 Apr 20 12:34 libaspell.so -> libaspell.so.15.0.2 lrwxrwxrwx 1 root root 19 Apr 20 12:34 libaspell.so.15 -> libaspell.so.15.0.2 -rwxr-xr-x 1 root root 8036610 Apr 20 12:34 libaspell.so.15.0.2 -rwxr-xr-x 1 root root 837 Apr 20 12:34 libpspell.la lrwxrwxrwx 1 root root 19 Apr 20 12:34 libpspell.so -> libpspell.so.15.0.2 lrwxrwxrwx 1 root root 19 Apr 20 12:34 libpspell.so.15 -> libpspell.so.15.0.2 -rwxr-xr-x 1 root root 6260 Apr 20 12:34 libpspell.so.15.0.2 bash-2.05a$ Thanks for the suggestion. Ian.
Just a thought, but according to README.claws included within the tarball, it stipulates that version 0.50 or newer of aspell is required. What version have you got on your system, Ian? -- Begin Quote --- a. Requirements --------------- Note: As for version 0.8.3 (and cvs version 0.8.2claws3), Sylpheed-Claws uses the new GNU/aspell 0.50 for spell checking instead of the obsolete pspell and old aspell 0.33.x. You will need to upgrade your system. See http://www.gnu.org/software/aspell for instructions on how to do this. The spell checker in Sylpheed requires the new GNU/aspell library (http://www.gnu.org/software/aspell), version 0.50 or newer. You also need the dictionaries. Check GNU/aspell home page for how to download and install them. NB: The old dictionaries used by the old aspell will not work. -- End Quote -- Ian Douglas wrote on 20 April 2003 19:17:
On Sunday, April 20, 2003 5:04 PM, Steve Fosdick wrote:
Ian Douglas wrote:
bash-2.05a$ ls /usr/local/lib X11 libaspell.so.15 libpspell.so libaspell.la libaspell.so.15.0.2 libpspell.so.15 libaspell.so libpspell.la libpspell.so.15.0.2
then...
configure:16202: ./conftest ./conftest: error while loading shared libraries: libaspell.so.15: cannot open shared object file: No such file or directory configure:16205: $? = 127 configure: program exited with status 127
I looks like the program is trying to load the shared library by using the name libaspell.so.15 whereas the library is probably actually in the file libaspell.so.15.0.2 libaspell.so.15 should be a symbolic link to libaspell.so.15.0.2 - if it isn't then this is probably the problem - you just need to remove libaspell.so.15 and re-link it.
Thanks for the tip Steve. However, unfortunately, it looks like the file is already linked:
bash-2.05a$ ls -l /usr/local/lib total 7884 drwxr-xr-x 3 root root 4096 Apr 18 16:22 X11 -rwxr-xr-x 1 root root 809 Apr 20 12:34 libaspell.la lrwxrwxrwx 1 root root 19 Apr 20 12:34 libaspell.so -> libaspell.so.15.0.2 lrwxrwxrwx 1 root root 19 Apr 20 12:34 libaspell.so.15 -> libaspell.so.15.0.2 -rwxr-xr-x 1 root root 8036610 Apr 20 12:34 libaspell.so.15.0.2 -rwxr-xr-x 1 root root 837 Apr 20 12:34 libpspell.la lrwxrwxrwx 1 root root 19 Apr 20 12:34 libpspell.so -> libpspell.so.15.0.2 lrwxrwxrwx 1 root root 19 Apr 20 12:34 libpspell.so.15 -> libpspell.so.15.0.2 -rwxr-xr-x 1 root root 6260 Apr 20 12:34 libpspell.so.15.0.2 bash-2.05a$
Thanks for the suggestion.
Ian.
_______________________________________________ main@lists.alug.org.uk http://www.alug.org.uk/ http://lists.alug.org.uk/mailman/listinfo/main Unsubscribe? See message headers or the web site above!
-- Affordable web hosting packages from Martyn Drake -> http://forum.movielad.co.uk/viewforum.php?f=2
On Sun, 20 Apr 2003, Martyn Drake wrote:
Just a thought, but according to README.claws included within the tarball, it stipulates that version 0.50 or newer of aspell is required. What version have you got on your system, Ian?
The other option is that /usr/local/lib isn't in /etc/ld.so.conf or that ldconfig hasn't been run since it was added. I would expect slackware to use /usr/local for some apps already, so it's prolly a longshot... BenE
On Sunday 20 April 2003 10:35 pm, BenE wrote:
The other option is that /usr/local/lib isn't in /etc/ld.so.conf or that ldconfig hasn't been run since it was added.
I would expect slackware to use /usr/local for some apps already, so it's prolly a longshot...
Thanks for the suggestion BenE. I have had a look in /etc/ld.so.conf and can see: root@parka:~# cat /etc/ld.so.conf /usr/local/lib /usr/X11R6/lib /usr/i386-slackware-linux/lib /opt/kde/lib /usr/lib/qt/lib I then ran ldconfig just to be on the safe side: root@parka:~# ldconfig and retried: ./configure --enable-aspell make make install However the spell-checker is now no loger grayed out in the "compose new mail" window, it is now completely missing, when I restarted sylpheed. Ian.
On Sunday, April 20, 2003 7:53 PM, Martyn Drake said:
Just a thought, but according to README.claws included within the tarball, it stipulates that version 0.50 or newer of aspell is required. What version have you got on your system, Ian?
Hi Martyn, I think I am using 0.5: bash-2.05a$ aspell -v @(#) International Ispell Version 3.1.20 (but really Aspell 0.50.3) *HOWEVER*
-- Begin Quote --- a. Requirements --------------- Note: As for version 0.8.3 (and cvs version 0.8.2claws3), Sylpheed-Claws uses the new GNU/aspell 0.50 for spell checking instead of the obsolete pspell and old aspell 0.33.x. You will need to upgrade your system. See http://www.gnu.org/software/aspell for instructions on how to do this.
The spell checker in Sylpheed requires the new GNU/aspell library (http://www.gnu.org/software/aspell), version 0.50 or newer.
Yep, think I upgraded Aspell ok.
You also need the dictionaries. Check GNU/aspell home page for how to download and install them.
NB: The old dictionaries used by the old aspell will not work.
Oooooopppps! Guess who has forgotten to also upgrade his dictionaries! Could this be the problem... New Aspell but old dictionaries??? Thanks for spotting that. Will upgrade my dictionaries tomorrow and retry the compile! Ian.
On Sunday 20 April 2003 9:47 pm, I wrote:
Oooooopppps! Guess who has forgotten to also upgrade his dictionaries! Could this be the problem... New Aspell but old dictionaries??? Thanks for spotting that. Will upgrade my dictionaries tomorrow and retry the compile!
Hi folks, I have just upgraded my Aspell dictionaries. I then cd into my sylpheed-claws tarball directory and ran configure: ./configure --enable-aspell This time the spelling section looked ok: configure:15968: checking whether to use GNU/aspell configure:15971: result: yes configure:16043: checking for aspell configure:16061: found /usr/local/bin/aspell configure:16074: result: /usr/local/bin/aspell configure:16082: checking for GNU/aspell - version >= 0.50 configure:16127: gcc -o conftest -g -O2 conftest.c >&5 configure:16130: $? = 0 configure:16132: ./conftest configure:16135: $? = 0 configure:16150: result: yes configure:16152: checking for GNU/aspell dictionaries location configure:16160: result: /usr/local/lib/aspell configure:16162: checking if GNU/aspell is correctly installed configure:16197: gcc -o conftest -g -O2 -I/usr/local/include conftest.c -L/usr/local/lib -laspell >&5 configure:16200: $? = 0 configure:16202: ./conftest configure:16205: $? = 0 configure:16222: result: yes The little summary table at the end of the ./configure process said: sylpheed 0.8.11claws image support : yes (gdk-pixbuf) GnuPG : no JPilot : no LDAP : no OpenSSL : no iconv : yes compface : no IPv6 : no GNU/aspell : no Crash dialog : no Plugins : The binary will be installed in /usr/local/bin Configure finished, type 'make' to build. I then done a "make" followed by a "make install" and restarted Sylpheed however, unfortunately, the "Spelling" menu is now completely missing (rather than just being greyed-out) in the "compose new email" window. Very frustrating! Ian.
Spell Checking may be working but just not configured:
Start Sylpheed Click on "Configuration" menu Click on "Common Preferences" Click on "Spell Checker" Click on "Enable Spell Checker" Make sure "Default Dictionary" is set to "en_GB" Click on "OK"
Aha! Got it! Thanks for that! Obvious when you know how! Spell Checker is now up and running. Thanks everyone for all your help! Ian.
participants (4)
-
BenE -
Ian Douglas -
Martyn Drake -
Steve Fosdick