From: Jelle Licht <jlicht@posteo.net>
To: Andy Tai <atai@atai.org>
Cc: 46376@debbugs.gnu.org
Subject: [bug#46376] [PATCH] gnu: tesseract-ocr: update to 4.1.1)
Date: Tue, 09 Feb 2021 23:43:06 +0100 [thread overview]
Message-ID: <86sg6450cl.fsf@posteo.net> (raw)
In-Reply-To: <CAJsg1E_usROdu14HbS2SV2hjrOggwdyKr=KmFxuVRGinJwyOMg@mail.gmail.com>
Hi Andy,
Andy Tai <atai@atai.org> writes:
> Hi, I updated the patch to only build in serial, with "-j 1"
>
> and with this, everything, including tests, builds successfully.
No such luck, for me at least. Are you certain you got it to build on
your end? Could you try with `--check`?
I've had to work out the following things:
- Patched out "<tesseract/baseapi.h>" and "<tesseract/helpers.h>" to
refer to "baseapi.h" and "helpers.h" in "unittest/pagesegmode_test.cc".
- Make sure the check phase takes place after running "make training" in
a phase.
I still ended up with several failing tests, courtesy of it running
unsupported instructions on my cpu (educated guess: avx etc). Nothing
comes easy, I guess.
Thanks,
- Jelle
next prev parent reply other threads:[~2021-02-09 22:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 6:32 [bug#46377] [PATCH] gnu: tesseract-ocr: update to 4.1.1 Andy Tai
2021-02-08 6:42 ` [bug#46376] " Andy Tai
[not found] ` <handler.46376.B.161276666727875.ack@debbugs.gnu.org>
2021-02-08 6:51 ` [bug#46376] [PATCH] gnu: tesseract-ocr: update to 4.1.1) Andy Tai
2021-02-08 21:36 ` Jelle Licht
2021-02-08 23:14 ` Andy Tai
2021-02-09 11:56 ` Jelle Licht
2021-02-09 16:22 ` Andy Tai
2021-02-09 22:43 ` Jelle Licht [this message]
2021-02-09 22:53 ` Andy Tai
2021-02-10 7:52 ` Andy Tai
2021-02-11 0:00 ` Andy Tai
2021-02-11 10:48 ` Jelle Licht
2021-02-11 18:34 ` Andy Tai
2021-02-13 14:34 ` bug#46376: " Jelle Licht
2021-02-13 20:37 ` [bug#46376] " Andy Tai
[not found] ` <handler.46377.B.161277624811801.ack@debbugs.gnu.org>
2021-02-08 17:53 ` [bug#46377] Acknowledgement ([PATCH] " Andy Tai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86sg6450cl.fsf@posteo.net \
--to=jlicht@posteo.net \
--cc=46376@debbugs.gnu.org \
--cc=atai@atai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.