[tesseract-ocr] Re: Tesseract 4.0 on Alpine Linux Docker Container

2018-04-12 Thread Kalven Schraut
also looks like calling configure with the --disable-openmp prevents the seg fault which allows me to continue to use tesseract for now would still like to figure out why the seg fault is occuring with multiple threads. On Thursday, April 12, 2018 at 8:23:06 PM UTC-5, Kalven Schraut wrote

[tesseract-ocr] Re: Tesseract 4.0 on Alpine Linux Docker Container

2018-04-12 Thread Kalven Schraut
, Kalven Schraut wrote: > > I am attempting to use tesseract's API in my project and everything works > as expected on ubuntu when running the code, but I am receiving a seg fault > when I moved everything over to an alpine docker container. > > The backtrace

[tesseract-ocr] Re: Tesseract 4.0 on Alpine Linux Docker Container

2018-04-11 Thread Kalven Schraut
nload.sh to download my data On Tuesday, April 10, 2018 at 7:29:31 AM UTC-5, Kalven Schraut wrote: > > I am attempting to use tesseract's API in my project and everything works > as expected on ubuntu when running the code, but I am receiving a seg fault > when I moved everythi

[tesseract-ocr] Tesseract 4.0 on Alpine Linux Docker Container

2018-04-10 Thread Kalven Schraut
I am attempting to use tesseract's API in my project and everything works as expected on ubuntu when running the code, but I am receiving a seg fault when I moved everything over to an alpine docker container. The backtrace from the segfault: #0 0x72c4a50a in ?? () from /usr/lib/libgomp