-
Notifications
You must be signed in to change notification settings - Fork 74
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
Error getting setup #3
Comments
Ok so, about the About the
This is the list of tesseract headers on my system. |
Thanks for jumping in here to help, sadly I'm still not quite there. (btw, I have been testing the command line version of tesseract and it seems to be working great) So I looked into the MacPorts directory and it looks like I had all the headers that you listed above. For the fun luck of it all I went ahead and uninstalled Tesseract from Port and built it from source. This actually gave me a new error, this time I was missing a header file in Leptonica which is still installed via Port. My guess is that with ffi-inliner somehow can't find the path to the headers in I'm currently working on building Leptonica from source to see if that fixes the issues and will rebuild Tesseract once that is done. In the meantime, do you have any thoughts on why ffi-inliner wouldn't be able to see those headers? Attached is the IRB error and the compile error
|
It's probably because gcc's include path doesn't include |
Ok, pushed a new version of |
I am having this issue as well when I require tesseract. Can you explicitly tell me how to fix this issue? Not sure where to export CFLAGS - before I do the gem install tesseract? How can I tell if I have the dependencies in the right place? Any help is appreciated. |
I installed the libraries using homebrew. Is there a way to tell the gem that the libraries are installed somewhere else? /usr/local/Cellar? |
You either do the following in the shell before running the application
Or set them before requiring tesseract like below
|
works - thank you! |
Solution for Redhat installation of leptonica and tesseract with the correct arguments to make it run inspired from this .sh install file which did not work completely for me yum -y update
yum -y install libstdc++ autoconf automake libtool autoconf-archive pkg-config gcc gcc-c++ make libjpeg-devel libpng-devel libtiff-devel zlib-devel
#Install AutoConf-Archive
wget ftp://mirror.switch.ch/pool/4/mirror/epel/7/ppc64/a/autoconf-archive-2016.09.16-1.el7.noarch.rpm
rpm -i autoconf-archive-2016.09.16-1.el7.noarch.rpm
# install leptonica from github
wget https://github.com/DanBloomberg/leptonica/archive/v1.72.tar.gz
tar -zxvf v1.72.tar.gz
cd leptonica-1.72
chmod +x configure # this is only if you have permission problems.
./configure --prefix=$HOME/local/
make
make install
cd ..
# install tesseract from github
wget https://github.com/tesseract-ocr/tesseract/archive/3.04.01.tar.gz
tar -zxvf 3.04.01.tar.gz
cd tesseract-3.04.01/
./autogen.sh
LIBLEPT_HEADERSDIR=$HOME/local/include ./configure --prefix=$HOME/local/ --with-extra-libraries=$HOME/local/lib
make
make install
Any poor soul that finds this in the future, I hope this helps. This will solve this issue and issue #32 |
Hey there, I'm really grateful that you've put together this gem. I'm looking to do some OCR work for a grad school project and would love to be working in Ruby and Tesseract seems like the right OCR library to be working with.
So far I'm having a hard time getting up and running though. Below are the crashes that happen when I try to include 'tesseract or 'tesseract-ocr' in IRB. Could you take a look at what I'm doing and see if there's anything apparently wrong?
FYI things I know/am running
When I try to include Tesseract in a IRB it throws the follow error:
And when I require Tesseract-OCR I get this error:
The results of that log look like:
I believe I've correctly pulled down your version of ffi-inline and installed it but that could be the sticking point. I also noticed that a few commits back you changed the gemspec to no longer require ffi-inliner but ffi-inline instead yet in the c.rb file it's using ffi-inliner. I'm kind of a newb so maybe that isn't the problem.
Any thoughts?
The text was updated successfully, but these errors were encountered: