Am 18.07.2014 um 12:12 schrieb Fabio Fiorelli <ff...@cam.ac.uk>: > I've retried after forcing the install of a more recent version of the > developer package, and now it seems that the flag for hunspell is thrown. > > Fabio
So, the LyX side if the story is as it should be. Your first configure attempt failed to compile the LyX with the hunspell library. Consequently there is no hunspell spell checker and if no other spell checker is available the list of the available spell checkers is empty and the chooser widget is disabled. Because of the missing hunspell the hunspell path input field is disabled too. configure:14279: checking hunspell/hunspell.hxx usability conftest.cpp:157:33: error: hunspell/hunspell.hxx: No such file or directory | #include <hunspell/hunspell.hxx> configure:14279: checking hunspell/hunspell.hxx presence conftest.cpp:124:33: error: hunspell/hunspell.hxx: No such file or directory | #include <hunspell/hunspell.hxx> configure:14279: checking for hunspell/hunspell.hxx configure:14291: checking for main in -lhunspell configure:14310: g++ -o conftest -g -O2 -Wextra -Wall conftest.cpp -lhunspell -lz >&5 /usr/bin/ld: cannot find -lhunspell configure:14328: checking whether to use hunspell ac_cv_header_hunspell_hunspell_hxx=no ac_cv_lib_hunspell_main=no USE_HUNSPELL_FALSE='' USE_HUNSPELL_TRUE='#' The second attempt now is successful. configure:10773: checking for HUNSPELL configure:10781: $PKG_CONFIG --exists --print-errors "hunspell" configure:10799: $PKG_CONFIG --exists --print-errors "hunspell" configure:10942: checking whether to use hunspell ac_cv_env_HUNSPELL_CFLAGS_set= ac_cv_env_HUNSPELL_CFLAGS_value= ac_cv_env_HUNSPELL_LIBS_set= ac_cv_env_HUNSPELL_LIBS_value= pkg_cv_HUNSPELL_CFLAGS='-I/usr/include/hunspell ' pkg_cv_HUNSPELL_LIBS='-lhunspell-1.2 ' HUNSPELL_CFLAGS='-I/usr/include/hunspell ' HUNSPELL_LIBS='-lhunspell-1.2 ' USE_HUNSPELL_FALSE='#' USE_HUNSPELL_TRUE='' VERSION_INFO='Configuration\n Host type: i686-pc-linux-gnu\n Special build flags: build=release use-hunspell\n C++ Compiler: g++ (4.4.7)\n C++ Compiler LyX flags: \n C++ Compiler flags: -O2\n Linker flags: \n Linker user flags: \n Qt 4 Frontend:\n Qt 4 version:\t\t4.6.2\n Packaging: posix\n LyX binary dir: /usr/local/bin\n LyX files dir: /usr/local/share/lyx\n' #define USE_HUNSPELL 1 #define VERSION_INFO "Configuration\n Host type: i686-pc-linux-gnu\n Special build flags: build=release use-hunspell\n C++ Compiler: g++ (4.4.7)\n C++ Compiler LyX flags: \n C++ Compiler flags: -O2\n Linker flags: \n Linker user flags: \n Qt 4 Frontend:\n Qt 4 version:\t\t4.6.2\n Packaging: posix\n LyX binary dir: /usr/local/bin\n LyX files dir: /usr/local/share/lyx\n" It is possible to send a message to the terminal to notify the packager of the missing spell checker libraries. Stephan > On 07/18/2014 10:50 AM, Stephan Witt wrote: >> Am 18.07.2014 um 11:43 schrieb Fabio Fiorelli <ff...@cam.ac.uk>: >> >>> This are screenshots from a machine in which LyX 2.1.0 was installed with >>> Hunspell already in. The procedure I use is simply >>> • tar the archive >>> • Enter the unpacked folder >>> • Use ./configure >>> • check it gives no error flag. >>> • make (I use the regular make as I'm not familiar with cmake) >>> • make install as su >> Please provide the config.log. >> >> Can you please double-check that the hunspell package *for developers* is >> installed? >> If this is not the case then retry after installing them. >> Then check the output of your configure run if it differs from the previous >> one. >> >> Stephan >> >>> On 07/17/2014 11:25 PM, Jean-Marc Lasgouttes wrote: >>>> Le 17/07/14 18:35, Fabio Fiorelli a écrit : >>>>> Hi Jean Marc. There seem to be no additional flags required. >>>>> Configuration >>>>> Host type: i686-pc-linux-gnu >>>>> Special build flags: build=release use-hunspell >>>>> C++ Compiler: g++ (4.4.7) >>>>> C++ Compiler LyX flags: >>>>> C++ Compiler flags: -O2 >>>>> Linker flags: >>>>> Linker user flags: >>>>> Qt 4 Frontend: >>>>> Qt 4 version: 4.6.2 >>>>> Packaging: posix >>>>> LyX binary dir: /usr/local/bin >>>>> LyX files dir: /usr/local/share/lyx >>>>> >>>>> In fact I tested it right now in another virtual machine. >>>>> Lyx 2.1.1 installs correctly with access to hunspell without any further >>>>> configuration, while Lyx 2.1 doesn't. >>>>> Should I go forward? Thank you for your understanding. >>>> It is very weird... So USE_HUNSPELL is defined in config.h (in build >>>> directory°? >>>> >>>> If so, I wonder why the entry is greyed out. Could you provide a >>>> screenshot? >>>> >>>> JMarc >>> <engine.jpeg><path.jpeg> > > <config.log><config-after.log>
