Bug#797092: woo: FTBFS on non-x86: inappropriately builds with -march=core2
Aaron M. Ucko
ucko at debian.org
Fri Sep 4 04:36:15 UTC 2015
notfixed 797092 1.0-2
found 797092 1.0-2
thanks
"Aaron M. Ucko" <ucko at debian.org> writes:
> Builds of woo for non-x86 architectures all failed due to trying to
> invoke the compiler with the x86-specific flag -march=core2. This
> flag isn't appropriate even on x86, because it limits the portability
> of the resulting binaries, so please leave it off altogether.
Thanks for looking into this issue. I see you wound up substituting
-march=native, which is no better:
* It still limits the portability of the resulting binaries.
* It is also available only on x86.
* It affects reproducibility, because binaries will vary depending on
the precise CPU type of the build system.
Could you please not pass any -march flag?
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?amu@monk.mit.edu
More information about the debian-science-maintainers
mailing list