"Joseph S. Myers" <jos...@codesourcery.com> writes:

> In general link tests *are* required for GNU/Linux targets, because of 
> e.g. uClibc configurations where some functions may be disabled and this 
> can sometimes only be detected through a link test.  Furthermore, when 
> building shared libraries you need a shared libc to link them against, 
> which means that in that case link tests will need to work anyway.

In those cases we need to be producing sensible error messages, not
inexplicable messages resulting from bad interactions of our complex
configuration software.

Ian

Reply via email to