Your message dated Fri, 10 Jul 2015 00:14:49 -0700
with message-id 
<CAHjiUboubBiQKL1Z9=lzopvrpqaybn7pwc4ff5tgye6fnvw...@mail.gmail.com>
and subject line tesseract: source not compiled with -O2, significant 
performance decrease
has caused the Debian Bug report #775759,
regarding tesseract: source not compiled with -O2, significant performance 
decrease
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
775759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775759
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tesseract
Version: 3.02.01-6
Severity: normal

Dear Maintainer,

The debian/rules file for the tesseract package sets a custom CFLAGS
(also used as CXXFLAGS) which does not include -O2.  If I compile
tesseract source directly using the default CFLAGS="-g -O2" or if
I simply add -O2 to the debian/rules CFLAGS, we are showing an
approximate 50% reduction in time it takes to OCR an image.

Can the package be updated with -O2 ?

Thanks.


-- System Information:
Debian Release: 7.7
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
The build rule uses:

    dpkg-buildflags --get CFLAGS

This includes -O2, at least on the AMD64 architecture. I am
watching the package build right now and it is using -O2. I'm
guessing that I fixed this some time since the reported problem.
Please let me know if you disagree.

--- End Message ---

Reply via email to