Open ftyers opened 6 years ago
Hi Spectie,
Sorry for the delay in reviewing this, overall the changes look good, however unfortunately it doesn't currently build, here's the log output:
autoreconf: Entering directory '.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.ac,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:49: installing './compile'
configure.ac:15: installing './missing'
src/Makefile.am: installing './depcomp'
autoreconf: no config.status: cannot re-make
autoreconf: Leaving directory '.'
configure: WARNING: you should use --build, --host, --target
configure: WARNING: invalid host type: ./autogen.sh
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... yes
./configure: line 2952: ]: command not found
checking for style of include used by make... GNU
checking for ./autogen.sh-gcc... no
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for ./autogen.sh-g++... no
checking for ./autogen.sh-c++... no
checking for ./autogen.sh-gpp... no
checking for ./autogen.sh-aCC... no
checking for ./autogen.sh-CC... no
checking for ./autogen.sh-cxx... no
checking for ./autogen.sh-cc++... no
checking for ./autogen.sh-cl.exe... no
checking for ./autogen.sh-FCC... no
checking for ./autogen.sh-KCC... no
checking for ./autogen.sh-RCC... no
checking for ./autogen.sh-xlC_r... no
checking for ./autogen.sh-xlC... no
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking build system type... Invalid configuration ./autogen.sh': machine
./autogen.sh' not recognized
configure: error: /bin/bash ./config.sub ./autogen.sh failed
configure failed
Note also: ./configure: line 2952: ]: command not found
(which appears to be caused by a stray ] in configure.ac line 41)
I'm also a little curious as to the --enable-tensorflow option, in what circumstance would the user not want to link against libtensorflow_cc, since it's required by the deepspeech library?
Thanks, Mike
I've added a configure option to point to where deepspeech is. I've also removed two generated files.