configure disables both supports when "--disable-aspell --enable-hunspell" is passed

[GoogleCodeExporter]

When running configure with "--disable-aspell --enable-hunspell" it finally 
builds without any support:
link-grammar-4.6.6

    prefix:                         /usr/local
    compiler:                       gcc  -g -O2 -std=c99 -D_BSD_SOURCE 
-D_SVID_SOURCE -D_GNU_SOURCE
    autopackage:                    no
    Posix threads:                  no
    Editline command-line history:  no
    Java interfaces:                yes
    ASpell spell checker:           no
    HunSpell spell checker:         no
    HunSpell dictionary location:   
    Boolean SAT solver:             no
    Corpus statistics database:     no

I would expect, instead, being able to configure hunspell/aspell support 
simply using different combinations of --enable/disable in configure

Thanks a lot

Original issue reported on code.google.com by pachora...@gmail.com on 23 Mar 2010 at 2:37

Attachments:

• config.log

[GoogleCodeExporter]

Thanks for the report.
I've pushed a fix to svn, it will be in the next release (4.6.7)

The patch I applied is below; if you want to try it, then apply the patch and 
run
./autogen.sh to rebuild configure.

===================================================================
--- configure.in  (revision 28579)
+++ configure.in  (working copy)
@@ -142,14 +142,15 @@
 do_aspell=yes
 AC_ARG_ENABLE([aspell], [AS_HELP_STRING([--disable-aspell],
   [Build without ASpell support (default is enabled)])],
-  do_aspell=no)
+  [do_aspell="${enableval}"])
+
 AM_CONDITIONAL(WITH_ASPELL, test x${do_aspell} = xyes)

 dnl Hunspell Support is handled here
 do_hunspell=yes
 AC_ARG_ENABLE([hunspell], [AS_HELP_STRING([--disable-hunspell],
-      [Build without HunSpell support (default is enabled)])],
-      do_hunspell=no)
+  [Build without HunSpell support (default is enabled)])],
+  [do_hunspell="${enableval}"])

 AM_CONDITIONAL(WITH_HUNSPELL, test x${do_hunspell} = xyes)

Original comment by linasvep...@gmail.com on 23 Mar 2010 at 4:13

• Changed state: Fixed

[GoogleCodeExporter]

Sadly it still fails after applying the patch:
./configure --enable-aspell --disable-hunspell

-> And I get:
link-grammar-4.6.6

    prefix:                         /usr
    compiler:                       x86_64-pc-linux-gnu-gcc  -march=native -O2 -
pipe -std=c99 -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE
    autopackage:                    no
    Posix threads:                  no
    Editline command-line history:  no
    Java interfaces:                yes
    ASpell spell checker:           no
    HunSpell spell checker:         no
    HunSpell dictionary location:   
    Boolean SAT solver:             no
    Corpus statistics database:     no

And the same with --disable-aspell --enable-hunspell :-(

Original comment by pachora...@gmail.com on 23 Mar 2010 at 8:10

[GoogleCodeExporter]

Sorry, I am not applying it ok

Sorry for the noise

Original comment by pachora...@gmail.com on 23 Mar 2010 at 8:12

[GoogleCodeExporter]

Seems that enabling both (aspell and hunspell) results in aspell being enabled 
and 
hunspell disabled, is it the expected behavior? In that case, configure help 
should 
be modified from:
  --disable-aspell        Build without ASpell support (default is enabled)
  --disable-hunspell      Build without HunSpell support (default is enabled)

to:
  --disable-aspell        Build without ASpell support (default is enabled)
  --disable-hunspell      Build without HunSpell support (default is disabled)

Thanks a lot for your attention :-)

Original comment by pachora...@gmail.com on 23 Mar 2010 at 8:18

[GoogleCodeExporter]

Actually, it will build with either. If both packages are found and installed, 
then
it will pick aspell over hunspell; otherwise it will use whichever of the two 
it finds. 

Original comment by linasvep...@gmail.com on 23 Mar 2010 at 11:10

[GoogleCodeExporter]

OK, thanks a lot for the info :-)

Original comment by pachora...@gmail.com on 24 Mar 2010 at 1:19