Anyway in other hand there is also a problem with libtool during installation. which libtool doesn't work (ubuntu & debian) but the package is up to date. deleting 'libtools' from extra/check_dependencies.sh do the work without problem.
Since this revision (https://sourceforge.net/p/kaldi/code/5110/) i got
this error :
/usr/bin/env: perl -w: No such file or directory
Anyway in other hand there is also a problem with libtool during
installation. which libtool doesn't work (ubuntu & debian) but the package
is up to date. deleting 'libtools' from extra/check_dependencies.sh do the
work without problem.
BTW, to explain:
Dan recently changed all perl and python script to use the perl/python
interpreter that is first on path, not the system one. That is needed when
you have a local install of perl/python.
It seems, however, that not all env commands are interpreting the command
the way it's assumed -- some of them look for command "perl -w", others
just "perl" which is then run with parameter "-w"
Since this revision (https://sourceforge.net/p/kaldi/code/5110/) i got
this error :
/usr/bin/env: perl -w: No such file or directory
Anyway in other hand there is also a problem with libtool during
installation. which libtool doesn't work (ubuntu & debian) but the package
is up to date. deleting 'libtools' from extra/check_dependencies.sh do the
work without problem.
Since this revision ( https://sourceforge.net/p/kaldi/code/5110/ ) i got this error :
/usr/bin/env: perl -w: No such file or directory
Anyway in other hand there is also a problem with libtool during installation. which libtool doesn't work (ubuntu & debian) but the package is up to date. deleting 'libtools' from extra/check_dependencies.sh do the work without problem.
Edit :
For libtool : https://github.com/claritylab/sirius/issues/58
Last edit: Maxime ROBIN 2015-06-03
Maxime, thanks for letting us know, I will fix that.
y.
On Wed, Jun 3, 2015 at 9:37 AM, Maxime ROBIN maximerobin@users.sf.net
wrote:
BTW, to explain:
Dan recently changed all perl and python script to use the perl/python
interpreter that is first on path, not the system one. That is needed when
you have a local install of perl/python.
It seems, however, that not all env commands are interpreting the command
the way it's assumed -- some of them look for command "perl -w", others
just "perl" which is then run with parameter "-w"
y.
On Wed, Jun 3, 2015 at 9:37 AM, Maxime ROBIN maximerobin@users.sf.net
wrote:
Yeah i've already look what creates this problem. Thanks for your fast response. I hope it's not gonna be hard to fix. Good luck !
Maxime, I've just committed a fix to this, can you please update kaldi and
try?
y.
On Wed, Jun 3, 2015 at 10:02 AM, Maxime ROBIN maximerobin@users.sf.net
wrote:
Your fix works on ubuntu not on debian.
My test:
Last edit: Maxime ROBIN 2015-06-03
OK, perhaps I didn't get all occurrences. Can you tell me which script is
it? y.
On Wed, Jun 3, 2015 at 10:21 AM, Maxime ROBIN maximerobin@users.sf.net
wrote:
OK maybe i had a bug on my debian. Wait i retest it.
I tested on debian it's ok thanks for your help.
Regarding libtool: I'm using Debian 8 (Jessie) and I also needed to install libtool-bin.