I for one am not adverse to your proposition of separating the ming (mno-cygwin) functionality into its own script or program. This would reduce cygwin gcc's complexity and make it easier to port to cygwin and hopefully, mean nearer gcc versions faster. And by branching off the mno-cygwin, it can be delevoped and maintained at its own pace.
As mentioned it will caused some problems with existing build scripts I've written, but in time the bifricated situation will trickle down to be normal in time, I should think. Regards, Henman -------------------------------- RE: On 2/2/07, Christopher Faylor <[EMAIL PROTECTED]> wrote: -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
