No, the only thing --without-python does is prevent it from trying to build the Python module.
In fact the check for Python in the configure file should be fixed, at the moment it just checks for a 'python' executable, when in fact it needs to be checking for the Python development headers.
Also --without-lapack has no serious side effects. The LAPACK support is currently only used for Sphinx3 with full-covariance models, which are not widely used.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
i compiled sphinxbase and pocketsphinx succesfully with the given configure script and make on my linux PC.
Then i tried to cross compile it for an embedded System with arm11 Core on my host platform. But making sphinxbase failed.
my preparations:
the toolchain works
Path to ARM- GCC is in $PATH
export CC=arm-1136jfs-linux-gnueabi-gcc
cd sphinxbase;
./configure --host=arm-1136jfs-linux-gnuabi --enable-fixed --disable-shared;
make;
Result: It faild in Makefile sphinxbase/python:
Making all in python
make[1]: Entering directory `/home/srief/test_ps_0_5_sb_0_4/sphinxbase/python'
test -z "" || cp "./sphinxbase.c" sphinxbase.c
/usr/bin/python setup.py build
running build
running build_ext
building 'sphinxbase' extension
creating build
creating build/temp.linux-i686-2.4
arm-1136jfs-linux-gnueabi-gcc -fno-strict-aliasing -DNDEBUG -g -O2 -Wall -Wstrict-prototypes -fPIC -I..//include -I../include -I/usr/include/python2.4 -c sphinxbase.c -o build/temp.linux-i686-2.4/sphinxbase.o
CROSS COMPILE Badness: /usr/include in INCLUDEPATH: /usr/include/python2.4
error: command 'arm-1136jfs-linux-gnueabi-gcc' failed with exit status 1
make[1]: *** [pymod-build-stamp] Fehler 1
make[1]: Leaving directory `/home/srief/test_ps_0_5_sb_0_4/sphinxbase/python'
make: *** [all-recursive] Fehler 1
It looks like gcc includes the wrong header- files.
But i don`t know how i can set the correct PATH.
Are the configure options ok?
Hope for some Help in my first embedded Project.
thanks
Sebatian
thanks a lot,
pocketsphinx is compiled sucessfully. But not yet testet on target.
Can there be side-effects caused by --without-python?
No, the only thing --without-python does is prevent it from trying to build the Python module.
In fact the check for Python in the configure file should be fixed, at the moment it just checks for a 'python' executable, when in fact it needs to be checking for the Python development headers.
Also --without-lapack has no serious side effects. The LAPACK support is currently only used for Sphinx3 with full-covariance models, which are not widely used.
Try adding --without-python (and also --without-lapack, which will make the library smaller) to the configure line.