On Jan 16, 10:56 pm, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > Does anyone have an idea why -fno-strict-aliasing is turned off when
> > cross compiling?
>
> Because detection of -fno-strict-aliasing is made through running
> the compiler output (AC_TRY_RUN, see configure.in instead). For
> c
Does anyone have an idea why -fno-strict-aliasing is turned off when
cross compiling?
in configure generated for 2.4.4:
case $GCC in
yes)
# Python violates C99 rules, by casting between incompatible
# pointer types. GCC may generate bad code as a result of that,
# so use -fno-strict-a
