Package: tesseract Version: 4.1.0-1 Severity: serious Tags: patch
I recently discovered that tesseract 4.1.1-1 failed the armv7 contamination check we run in raspbian. Investigating shows that since version 4.1.0-1 tesseract started using -march=native. This compiler option is totally inappropriate for a binary distribution like Debian or Raspbian, because it means that the minimum CPU requirements of the resulting binaries will depend on what CPU the buildbox happens to have. 4.1.0-1 was never built in raspbian, I am not sure why 4.1.0-2 passed the contamination check in raspbian. My best guess is that -march=native on arm is poorly implemented and does not recognise the CPUs on some of our buildboxes. Anyway I whipped up a fix and uploaded it to raspbian. A debdiff should appear soon at https://debdiffs.raspbian.org/main/t/tessarect/
