> Apart from [using platform-based tests], I can't see any other
> solution for this problem. Doing a runtime test on the build/host platform
> for a feature of the target platform is simply wrong...

This still feels like a brittle solution to me.

I believe that testing what your actual machine does and does not support is 
the right approach when not cross-compiling.  I appreciate that some people 
may disagree here but if you do agree, then surely the same applies when 
cross-compiling and the only issue is how to implement such an approach?

So, I'll ask again:

Can we split our autoconf scripts into two parts: one to be run on the host 
machine and one to be run on the test machine?

--
Alastair

_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to