-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
Several non-descript cases of "core::Error" while compiling with GCC 10.3 in MSYS2 #3594
Comments
The reason is simple: it's not caused by the Tesseract source code, but a problem of the compiler, either not enough RAM or a compiler bug. |
It looks like you used a parallel build. I suggest to try a single threaded build. |
So I did, but it still produced such an error. |
Testing on a second PC. Here, after a lot of updates, same error for cargo building a rust project, and ccache seems to crash with OS error 3. I guess I have to purge the whole msys64 tree and reinstall it. Will refresh both PCs and tell later. |
Disabling the ccache might also help. |
But that may hurt compiling a few dozen of other projects ffmpeg is made of. Furthermore, it has never been an issue during the last few years. |
But none of this is tesseract problem. Problem is in the tools (compiler and build system) you chose. |
OK. A completely new MSYS2 in the suite fails as well. I'll see if they have an idea. PS: Reason seems to be msys2/MINGW-packages#9771 |
Environment
Current Behavior:
Several non-descript cases of "core::Error" while compiling with GCC 10.3:
See more verbose log files in logs.zip collected by media-autobuild_suite
I am a bit confused why it does not contain verbose C/C++ compiler errors with references to source lines. 🤔
Expected Behavior:
successful compilation
Suggested Fix:
none; I am not a C/C++ developer
The text was updated successfully, but these errors were encountered: