Re: [PATCH] Detect obsolete glibcs or kernel headers in libgomp configury (PR libgomp/26175, libgomp/26477)

[David Daney <ddaney at avtrex dot com>]

Mark Mitchell wrote:
> 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.

I think we are all on the same page here.

In addition to getting the same results from native and cross builds, it 
is important to be able to easily override configure.  Because on 
systems where cross-builds are likely it is also likely that there is a 
non-standard mix of kernel and libc.

David Daney