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

A question about missing dependency warnings when compiling and installing tesseract on centos using source code #388

Open
bruceyu0114 opened this issue May 7, 2024 · 1 comment

Comments

@bruceyu0114
Copy link

When centos uses source code compilation to install tesseract, three dependent packages are missing. However, these three dependent packages have been installed and the versions fully meet the requirements. This prevents me from installing the training tool.

the details of three wainings:
configure: WARNING: icu 52.1 or higher is required, but was not found.
configure: WARNING: Training tools WILL NOT be built.
configure: WARNING: Try to install libicu-dev package.
checking for pango... no
configure: WARNING: pango 1.38.0 or higher is required, but was not found.
configure: WARNING: Training tools WILL NOT be built.
configure: WARNING: Try to install libpango1.0-dev package.
checking for cairo... no
configure: WARNING: Training tools WILL NOT be built because of missing cairo library.
configure: WARNING: Try to install libcairo-dev?? package.

These three dependency packages are in my current centos environment:

rpm -q libicu pango cairo

libicu-60.3-2.1.al8.x86_64
pango-1.48.7-3.0.1.al8.x86_64
cairo-1.17.4-7.al8.x86_64
[root@iZbp1175f1gdn2130azzoi

Unfortunately, I tried it, both Tesseract4.1.0 and Tesseract5.3.0 have this problem.

Are there any environment variables that need to be configured for these three packages?

I tried, icu 52.1 was installed using source code compilation, and PKG_CONIFG_PATH was set in /etc/profile. The first dependency package warning could be resolved, but the remaining two dependency package warnings left me at a loss.

Looking forward to and thanking you for your answers.

@zdenop
Copy link
Contributor

zdenop commented May 7, 2024

try to read warning messages once again and compare them with output of our rpm command ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants