-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't build #64
Comments
Hello, I got the same issue. I tried to checkout to another commit by replacing "6417ac1dece94783e80dfbac0148604685d27579" to "9af2c5c16389e141f527ebde7ee432a0c1df9fb9", which is the commit done around the same date as the commit from "vosk/". But it fails to apply the "kaldi.patch". #10 [ 6/30] RUN git apply -v /tmp/kaldi.patch
#10 1.862 /tmp/kaldi.patch:230: trailing whitespace.
#10 1.862
#10 1.862 /tmp/kaldi.patch:232: trailing whitespace.
#10 1.862
#10 1.862 /tmp/kaldi.patch:269: trailing whitespace.
#10 1.862
#10 1.862 Checking patch src/Makefile...
#10 1.862 error: while searching for:
#10 1.862
#10 1.862 # Reset the default goal, so that the all target will become default
#10 1.862 .DEFAULT_GOAL :=
#10 1.862 all: $(SUBDIRS) matrix/test
#10 1.862 -echo Done
#10 1.862
#10 1.862 mklibdir:
#10 1.862
#10 1.862 error: patch failed: src/Makefile:41
#10 1.862 error: src/Makefile: patch does not apply
#10 1.862 Checking patch src/configure...
#10 1.863 Hunk #1 succeeded at 1026 (offset 4 lines).
#10 1.863 Checking patch src/ivector/ivector-extractor.cc...
#10 1.863 Checking patch src/makefiles/default_rules.mk...
#10 1.863 Checking patch src/makefiles/wasm_clapack.mk...
#10 1.863 Checking patch tools/Makefile...
#10 1.864 error: while searching for:
#10 1.864 # This new OS path is confirmed working on Windows 10 / Cygwin64.
#10 1.864 openfst_add_CXXFLAGS = -g -O2 -Wa,-mbig-obj
#10 1.864 else
#10 1.864 openfst_add_CXXFLAGS = -g -O3 -msse -msse2
#10 1.864 endif
#10 1.864
#10 1.864 openfst-$(OPENFST_VERSION)/Makefile: openfst-$(OPENFST_VERSION)
#10 1.864 cd openfst-$(OPENFST_VERSION)/ && \
#10 1.864 autoreconf -i && \
#10 1.864 ./configure --prefix=`pwd` $(OPENFST_CONFIGURE) CXX="$(CXX)" \
#10 1.864 CXXFLAGS="$(openfst_add_CXXFLAGS) $(CXXFLAGS)" \
#10 1.864
#10 1.864 error: patch failed: tools/Makefile:78
#10 1.864 error: tools/Makefile: patch does not apply
#10 1.864 Checking patch tools/extras/check_dependencies.sh...
#10 1.864 Checking patch tools/openfst.patch...
#10 1.864 /tmp/kaldi.patch:269: new blank line at EOF.
#10 1.864 +
#10 ERROR: executor failed running [/bin/sh -c git apply -v /tmp/kaldi.patch]: exit code: 1
------
> [ 6/30] RUN git apply -v /tmp/kaldi.patch:
#10 1.864 autoreconf -i && \
#10 1.864 ./configure --prefix=`pwd` $(OPENFST_CONFIGURE) CXX="$(CXX)" \
#10 1.864 CXXFLAGS="$(openfst_add_CXXFLAGS) $(CXXFLAGS)" \
#10 1.864
#10 1.864 error: patch failed: tools/Makefile:78
#10 1.864 error: tools/Makefile: patch does not apply
#10 1.864 Checking patch tools/extras/check_dependencies.sh...
#10 1.864 Checking patch tools/openfst.patch...
#10 1.864 /tmp/kaldi.patch:269: new blank line at EOF.
#10 1.864 +
------
ERROR: failed to solve: executor failed running [/bin/sh -c git apply -v /tmp/kaldi.patch]: exit code: 1
make: *** [Makefile:12: builder] Error 1 Any idea on which commit is the right one ? |
simonfn I have done the same workaround and I have the same error. I think repositories have changed since last summer and if you have not the builder installed, you cannot release. |
I guess I'll have to switch to forks of the repositories which I still have around. In the meantime you should be able to pull the builder image:
|
I tried to build the binary from the v.0.0.8 with the docker image from the v.0.0.6, but it fails with : 94 warnings and 1 error generated.
em++: error: '/emsdk/upstream/bin/clang++ -target wasm32-unknown-emscripten -DEMSCRIPTEN -fignore-exceptions -mllvm -combiner-global-alias-analysis=false -mllvm -enable-emscripten-sjlj -mllvm -disable-lsr -D__EMSCRIPTEN_major__=2 -D__EMSCRIPTEN_minor__=0 -D__EMSCRIPTEN_tiny__=29 -D_LIBCPP_ABI_VERSION=2 -Dunix -D__unix -D__unix__ -Werror=implicit-function-declaration -Xclang -iwithsysroot/include/SDL --sysroot=/emsdk/upstream/emscripten/cache/sysroot -Xclang -iwithsysroot/include/compat -std=c++17 -Wno-unused-function -I/opt/include -I/opt/kaldi/src -I/opt/kaldi/tools/openfst/include -I/io/src -O3 /io/src/../vosk/src/recognizer.cc -c -o /tmp/emscripten_temp_eh0ac_s_/recognizer_2.o' failed (returned 1)
make: *** [Makefile:90: /io/src/../build/release/vosk.bc] Error 1
make: Leaving directory '/io/src'
make: *** [Makefile:19: binary] Error 2 The v.0.0.7 and v.0.0.6 seems to work with the same build environnement with some warnings when compiling . |
I will try on my side and give feedbacks. Thanks a lot @ccoreilly. |
@olivierlaporte @simonfn could you test the branch in #66 ? |
@ccoreilly #66 worked for me, although it took quite some times to build the image |
It's also ok on my side. @ccoreilly Thanks you for your quick response and your very quick patch ! And like @simonfn building the image is quite long but it works. git checkout -b make-builder-reproducible origin/make-builder-reproducible
time make binary
|
Has anyone successfully implemented this functionality, |
It works just fine. You'd better describe what is your trouble in detail. |
Hello I try to reproduce the work produced by arbdevml for issue #49.
I fork the repository.
I have docker, make installed.
I reproduce the described steps :
I have the following output :
I think the kaldi project was updated and the git hash does not exists anymore
=> I check the rest of the Dockerfile file and i see that a clone of an inria repository is needed... but this repository seems to be not accessible ?
Someone can help me because i really want to help and have the voice fingerprinting feature with spk model that i have already experiment on python distro ?
The text was updated successfully, but these errors were encountered: