Hi, > I see the problem of builds which depend on an autobuilder which may be > different for each build. What would be the best solution for > distributions?
1) Special configuration option, which disables all CPU specific optimizations in compiler flags. or 2) Special configuration option, which disables all additional compiler flags which tesseract developers tends to add. Only compiler flags from system environment will be used in this case. For example, default compiler flags in Debian unstable now: $ dpkg-buildflags --get CXXFLAGS -g -O2 -fdebug-prefix-map=/home/boris=. -fstack-protector-strong -Wformat -Werror=format-security $ dpkg-buildflags --get CFLAGS -g -O2 -fdebug-prefix-map=/home/boris=. -fstack-protector-strong -Wformat -Werror=format-security $ dpkg-buildflags --get CPPFLAGS -Wdate-time -D_FORTIFY_SOURCE=2 $ dpkg-buildflags --get LDFLAGS -Wl,-z,relro But many (if not most of) packages are built with additional flags now, see: https://wiki.debian.org/Hardening > Suppress the code using a new configure option or some > magic which detects that the build is for a Debian distribution? This is never an option for Debian. Also do not forget about other GNU/Linux and *BSD distributions... Hope this helps. Best regards, Boris
