-fno-strict-aliasing turned off when cross compiling

["Martin v. Löwis"]

> This makes some sense. Thank you. As for this:
> 
>    def detect_modules(self):
>         # Ensure that /usr/local is always used
>         add_dir_to_list(self.compiler.library_dirs, '/usr/local/lib')
>         add_dir_to_list(self.compiler.include_dirs, '/usr/local/
> include')
> 
> it looks like a recipe for a disaster when cross compiling:
> cc1: warning: include location "/usr/local/include" is unsafe for
> cross-compilation

Yes, Python doesn't really support cross-compilation. So you are
on your own.

Of course, in true cross-compilation, you won't get a chance to run
setup.py, since python will only run on the target system, not on
the host system, therefore setup.py won't even start, and it doesn't
matter that it won't support cross-compilation.

Regards,
Martin