Am 20.01.2011 um 23:39 schrieb Stephan Witt: > Am 20.01.2011 um 19:39 schrieb Kenward Vaughan: > >> On Thu, 2011-01-20 at 19:33 +0100, Stephan Witt wrote: >>> Am 20.01.2011 um 18:33 schrieb Kenward Vaughan: >>> >>>> On Thu, 2011-01-20 at 18:03 +0100, Stephan Witt wrote: >>>>> Am 20.01.2011 um 17:56 schrieb Kenward Vaughan: >>>>> >>>>>> I'm a tad befuddled over this one... I suddenly discovered that I have >>>>>> no spellchecker, with either the system current version of LyX (1.6.7) >>>>>> or 2.0-b3 (I trade out ~/.lyx directories). I'm running Debian/Sid. >>>>>> >>>>>> I have both ispell and aspell installed. I've reconfigured LyX several >>>>>> times to no avail. I cannot change anything under Preferences > >>>>>> Spellchecker... the Spellchecker engine menu is greyed out. >>>>>> >>>>>> Changing language settings to English instead of Automatic, followed by >>>>>> restarting, reconfiguring, and restarting has no effect. >>>>>> >>>>>> :(( >>>>>> >>>>>> Is there something really basic here that I don't see?? >>>>> >>>>> Did you build LyX yourself? >>>>> If yes, how? And did you enable the spellchecker engines? >>>> >>>> >>>> I built the beta version myself and installed it using whatever defaults >>>> came with it. If spellchecking needs to be enabled, then it seems this >>>> ought to be a default instead of an option. >>> >>> You did not tell me, how you build it. >>> Nevertheless, please check you have all needed software packages for >>> developers installed. >>> In case you built it with autotools and configure you may want to check the >>> logs. >> >> >> The build ran fine after autoconfig was used. I glanced through the >> output, and seeing nothing odd ran make and then make install. All per >> the quick directions. > > I take it you called ./configure in top directory of source tree... > > The relevant output here is like > > ... > checking aspell.h usability... yes > checking aspell.h presence... yes > checking for aspell.h... yes > checking for new_aspell_config in -laspell... yes > checking whether to use aspell... yes > checking for ENCHANT... yes > checking whether to use enchant... yes > checking hunspell/hunspell.hxx usability... no > checking hunspell/hunspell.hxx presence... no > checking for hunspell/hunspell.hxx... no > checking for main in -lhunspell... no > checking whether to use hunspell... no > ... > > You can see I don't have any spell checker library code installed.
Sorry, should be: I don't have any "hunspell" spell checker library code installed > That's why hunspell is left not available. > > Please post the relevant output of your configure run for comparison. Stephan
