Skip to content
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

[DO NOT MERGE] Support openfst 1.8.2 #4829

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

georgthegreat
Copy link
Contributor

@georgthegreat georgthegreat commented Feb 23, 2023

This is a demonstration PR requested by @jtrmal in #4716.

There are only code changes, though we also have some CMakeLists changes needed to build kaldi via nixpkgs.

@jtrmal
Copy link
Contributor

jtrmal commented Feb 23, 2023 via email

@georgthegreat
Copy link
Contributor Author

I do not think there was any particular reason fo removing (though the same was done in #4716).

kaldi uses int32 (without _t) suffix from openfst, but openfst removed these aliases in 1.8.2 (I have no idea why this was done in a version changing patch number only).

I think that the intergration will be done version-by-version and we will be able to discuss the changes in the detailed PRs.

@jtrmal
Copy link
Contributor

jtrmal commented Feb 23, 2023 via email

@jtrmal
Copy link
Contributor

jtrmal commented Feb 23, 2023

I suppose we should leave this a few days as is, just to gather inputs from other people... @danpovey any opinion from you?

@galv
Copy link
Contributor

galv commented Feb 23, 2023

My only comment is that I'm not a big fan of polluting the global namespace with int32, etc. It can cause downstream pain for those who use kaldi as a library.

@danpovey
Copy link
Contributor

Is there demand for the latest version of OpenFST, or a concrete reason to upgrade?
I'm concerned that if we merge it, it will break existing builds and force people to try to update their OpenFST and recompile Kaldi. Together with the int32 change, it could break a lot of peoples' builds if they have integrated Kaldi into their projects. So there would have to be a fairly compelling reason to merge this into the master branch, IMO.

@h-vetinari
Copy link
Contributor

Just for cross-reference purposes, @mmcauliffe has a PR against this PR that could hopefully be considered here.

@mmcauliffe
Copy link
Contributor

So migrating to OpenFst 1.8.2 makes it a lot easier for us to get shared libraries working for Windows, and we additionally don't have to ship OpenFst 1.7.X libraries inside the kaldi package. I have everything building successfully on conda-forge here: conda-forge/kaldi-feedstock#38, but it'd be ideal to have these changes upstream.

@stale stale bot added the stale Stale bot on the loose label Jun 18, 2023
@danpovey
Copy link
Contributor

ping to keep it open, although we probably won't merge any time soon

@stale stale bot removed the stale Stale bot on the loose label Jun 18, 2023
@kkm000 kkm000 added the stale-exclude Stale bot ignore this issue label Aug 10, 2023
@kkm000
Copy link
Contributor

kkm000 commented Aug 10, 2023

Superseding: #4716

@kaldi-asr kaldi-asr deleted a comment from stale bot Aug 10, 2023
@kkm000
Copy link
Contributor

kkm000 commented Aug 10, 2023

@danpovey

ping to keep it open, although we probably won't merge any time soon

Dan, just slap the label stale-exclude Stale bot ignore this issue on it, and the bot will shut up. I don't know if there's a magic trick to add a label in an e-mail reply. Close: #1234 on a line by itself closes an issue, but that's all I know. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale-exclude Stale bot ignore this issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants