-
Notifications
You must be signed in to change notification settings - Fork 9.6k
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
make check fails with unittest/baseapi_test.cc:190: undefined reference #2439
Comments
latest code from master, built with
|
Linker error reported in issue tesseract-ocr#2439: unittest/baseapi_test.cc:190: undefined reference to `tesseract::TessBaseAPI::AdaptToWordStr(tesseract::PageSegMode, char const*)' Signed-off-by: Stefan Weil <[email protected]>
Please try pull request #2440. |
Updated to tesseract -v (Not yet updated with #2440) Now getting the following errors:
|
@Shreeshrii, I just tested it myself. The reported linker error is fixed. But there are lots of similar linker errors. |
We got the same result. :-) |
I will wait for your fix. :-) |
Linker error reported in issue tesseract-ocr#2439: unittest/baseapi_test.cc:190: undefined reference to `tesseract::TessBaseAPI::AdaptToWordStr(tesseract::PageSegMode, char const*)' Signed-off-by: Stefan Weil <[email protected]>
I think tests should be run with standard (default) setup (that does not modified API). |
Linker error reported in issue tesseract-ocr#2439: unittest/baseapi_test.cc:190: undefined reference to `tesseract::TessBaseAPI::AdaptToWordStr(tesseract::PageSegMode, char const*)' Signed-off-by: Stefan Weil <[email protected]>
Pull request #2441 fixes the build |
Linker error reported in issue #2439: unittest/baseapi_test.cc:190: undefined reference to `tesseract::TessBaseAPI::AdaptToWordStr(tesseract::PageSegMode, char const*)' Signed-off-by: Stefan Weil <[email protected]>
@stweil Thanks. Should I leave this issue open till that is fixed? |
Yes, please leave it open. |
Please see https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/tesseract-ocr/9HSpp7Ysduw/r8FPCHhBFAAJ as it might be related to this issue. |
I recently made a few changes related to this issue. Does someone want to test this and see if the issue of failing tests when the legacy engine is disabled still occurs? |
See #3226 for currently failing tests with --disable-legacy |
The text was updated successfully, but these errors were encountered: