David Daney wrote:
How about a configure option to force the desired configuration?
Jakub's already implemented that; we're just arguing about the default.
This situation seems similar to not being able to detect runtime TLS
support in a cross build (see the --enable-tls option).
Indeed; it's exactly the same situation.
My concern is the same there; if a cross-compiler does not produce the
same configuration as a native compiler, then debugging problems on
non-native systems becomes very difficult. A common way to debug a
problem with a native compiler is to build a cross compiler, and if you
actually get different behavior between the two, then that muddies the
waters. It's also common to have both native and cross compilers for
the same system, using some for on-target builds and some for other
aspects of development. Getting different behavior from the two is very
confusing.