The bug is about an optimisation flag that we shouldn't just get rid
of. At some point soon, I'll read the gcc manpage and figure out what
a proper flag for other architectures should be.
http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options
has the following to say about -march=native
/native/
This selects the CPU to tune for at compilation time by determining
the processor type of the compiling machine. Using -mtune=native
will produce code optimized for the local machine under the
constraints of the selected instruction set. Using -march=native
will enable all instruction subsets supported by the local machine
(hence the result might not run on different machines).
In other words this flag is totally inappropriate for a binary distribution
like debian.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
