On Wed, Jan 28, 2009 at 12:14:40AM -0600, Yaakov (Cygwin/X) wrote: >Charles Wilson wrote: >>This led to a suggestion that "--build=cygwin --host=mingw32" should >>always be interpreted as: mingw32-gcc is a cygwin-hosted cross >>compiler, NOT the native MinGW-project supported gcc (and if it IS the >>native MinGW one, expect breakage). I'm not sure such a sweeping >>statement is accurate, or wise -- will that assumption break people's >>exising (working) setups? > >If you're talking about configure gcc with those flags, then wouldn't >that usually mean that you're cross-compiling a regular, native MinGW >compiler? If you want a cygwin-hosted MinGW cross-compiler, you should >be using "--build=cygwin --host=cygwin --target=mingw32". I would be >hesitant to change the usual meaning of build/host just for >Cygwin/MinGW; I don't think we need to add to the confusion that most >people have about Cygwin.
Ditto. cgf -- 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/
