Installation of sequitur and mmseg fails (Prerequisites for GALE Mandarin)

[akshayc11]

I am not sure if this is system dependent, but here is my setup:
I have a custom pythonpath where I have installed virtualenv, from which I have created a separate virtual environment.

When I try to run

cd $KALDI_ROOT/tools
extras/install_sequitur.sh

I noticed that the installation script expects the setup.py to install the libraries at <sequitur_dir>/lib
However, the system installs it in <sequitur_dir>/lib64
A similar problem arose in the installation of mmseg

extras/install_mmseg.sh

Changing the installation lines that refer to lib/ to lib64/ fixed that issue for me.

I have attached a patch that I have created for that here. If you think this should be done, please feel free to apply the patch and commit it.

fix_extra_tool_install.patch.txt

Akshay

[jtrmal]

this is definitely system dependent. The patch itself is not valid for other systems. what system do you use? y.

…

On Thu, Jun 8, 2017 at 2:44 PM, Akshay Chandrashekaran < ***@***.***> wrote: I am not sure if this is system dependent, but here is my setup: I have a custom pythonpath where I have installed virtualenv, from which I have created a separate virtual environment. When I try to run cd $KALDI_ROOT/tools extras/install_sequitur.sh I noticed that the installation script expects the setup.py to install the libraries at <sequitur_dir>/lib However, the system installs it in <sequitur_dir>/lib64 A similar problem arose in the installation of mmseg extras/install_mmseg.sh Changing the installation lines that refer to lib/ to lib64/ fixed that issue for me. I have attached a patch that I have created for that here. If you think this should be done, please feel free to apply the patch and commit it. fix_extra_tool_install.patch.txt <https://github.com/kaldi-asr/kaldi/files/1062037/fix_extra_tool_install.patch.txt> Akshay — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1672>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKisX9w8CyWntwi69LN_oqhsx0UOuTDyks5sCED-gaJpZM4N0eCA> .

[danpovey]

The sequitur installation commands in install_sequitur.py explicitly select the current directory as the installation target: cd sequitur-g2p make CXX=g++ CC=gcc python setup.py install --prefix `pwd` cd ../ So I don't understand why it would install in lib64. Dan

…

On Thu, Jun 8, 2017 at 3:04 PM, jtrmal ***@***.***> wrote: this is definitely system dependent. The patch itself is not valid for other systems. what system do you use? y. On Thu, Jun 8, 2017 at 2:44 PM, Akshay Chandrashekaran < ***@***.***> wrote: > I am not sure if this is system dependent, but here is my setup: > I have a custom pythonpath where I have installed virtualenv, from which I > have created a separate virtual environment. > > When I try to run > > cd $KALDI_ROOT/tools > extras/install_sequitur.sh > > I noticed that the installation script expects the setup.py to install the > libraries at <sequitur_dir>/lib > However, the system installs it in <sequitur_dir>/lib64 > A similar problem arose in the installation of mmseg > > extras/install_mmseg.sh > > Changing the installation lines that refer to lib/ to lib64/ fixed that > issue for me. > > I have attached a patch that I have created for that here. If you think > this should be done, please feel free to apply the patch and commit it. > > fix_extra_tool_install.patch.txt > <https://github.com/kaldi-asr/kaldi/files/1062037/fix_extra_ tool_install.patch.txt> > > Akshay > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#1672>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/AKisX9w8CyWntwi69LN_ oqhsx0UOuTDyks5sCED-gaJpZM4N0eCA> > . > — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1672 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADJVu7v_yMy49KNbqP0is3o4Wzb39gI8ks5sCEW0gaJpZM4N0eCA> .

[akshayc11]

When you specify the prefix, I believe the setup.py creates a lib (in my case lib64) folder, into which it installs the python-specific site-packages. I believe the issue may be arising due to something akin to this: Linuxbrew/legacy-linuxbrew#443

I am building kaldi in a centOS instance (which is an RHEL fork)

One of the comments in the above issue was:

Looking at the Python bug tracker, this appears to be a change that certain Linux vendors make to their system Pythons to support mixed 32/64-bit systems. OpenSuSE does this; Ubuntu trusty (afaict, in my hands) does not. Apparently RHEL does. Linuxbrew or pyenv pythons should not.

I guess I am one of the unlucky few facing this issue.

[danpovey]

Hm. If some OSs still do this, I think it might be worthwhile fixing it in some way. @jtrmal, any chance you could make an 'issue'? Unless you disagree.

…

On Fri, Jun 9, 2017 at 4:48 AM, Akshay Chandrashekaran < ***@***.***> wrote: When you specify the prefix, I believe the setup.py creates a lib (in my case lib64) folder, into which it installs the python-specific site-packages. I believe the issue may be arising due to something akin to this: Linuxbrew/legacy-linuxbrew#443 <Linuxbrew/legacy-linuxbrew#443> This is being run on a centOS (which is an RHEL fork) One of the comments in the above issue was: Looking at the Python bug tracker, this appears to be a change that certain Linux vendors make to their system Pythons to support mixed 32/64-bit systems. OpenSuSE does this; Ubuntu trusty (afaict, in my hands) does not. Apparently RHEL does. Linuxbrew or pyenv pythons should not. I guess I am one of the unlucky few facing this issue. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1672 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADJVu5sL-yDWSnG__jMx9NMXm0y4ug7Cks5sCQb7gaJpZM4N0eCA> .

[jtrmal]

I will. I think it should be fairly easy to fix -- will look into it. y. On Fri, Jun 9, 2017 at 1:28 PM, Daniel Povey <[email protected]> wrote:

…

Hm. If some OSs still do this, I think it might be worthwhile fixing it in some way. @jtrmal, any chance you could make an 'issue'? Unless you disagree. On Fri, Jun 9, 2017 at 4:48 AM, Akshay Chandrashekaran < ***@***.***> wrote: > When you specify the prefix, I believe the setup.py creates a lib (in my > case lib64) folder, into which it installs the python-specific > site-packages. I believe the issue may be arising due to something akin to > this: Linuxbrew/legacy-linuxbrew#443 > <Linuxbrew/legacy-linuxbrew#443> > > This is being run on a centOS (which is an RHEL fork) > > One of the comments in the above issue was: > > Looking at the Python bug tracker, this appears to be a change that certain Linux vendors make to their system Pythons to support mixed 32/64-bit systems. OpenSuSE does this; Ubuntu trusty (afaict, in my hands) does not. Apparently RHEL does. Linuxbrew or pyenv pythons should not. > > I guess I am one of the unlucky few facing this issue. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <#1672 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ADJVu5sL-yDWSnG__ jMx9NMXm0y4ug7Cks5sCQb7gaJpZM4N0eCA> > . > — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1672 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKisXw0GZL5B6ybVDvm06kKugyGdza90ks5sCYC-gaJpZM4N0eCA> .

[jtrmal]

I created a fix for that. it would be great if @akshayc11 could test for lib64 case -- I tested for debian and seems to work for lib/ case.
y.

[akshayc11]

@jtrmal I tested the PR, and have added some comments there... Once those are addressed, I think the issue is fixed.

[johnjosephmorgan]

I am running the voxforge recipe. I am having a problem with sequitur. It looks like sequitur gets installed under $KALDI_ROOT/tools/sequitur-g2p, but the voxforge dictionary processing scripts expect sequitur to be under $KALDI_ROOT/tools/sequitur.