=== ----- Original Message ----- From: "Charles Wilson" <[EMAIL PROTECTED]> > > > > So, in this instance you'd have: > > > > /usr/H-i686-pc-cygwin/i686-pc-mingw32 > > > Yeah, but don't we want to *avoid* colliding with the GNUpro stuff? If > that's where Red Hat puts the various cygwin-hosted/other-target cross > compilers that come with GNUpro, shouldn't we pick something ELSE?
I dunno, but maybe :}. FWIW, I usually place such things in /usr/local/<target> and then symlink binaries etc to /usr/local/bin. For a package, I'd have no objection to a mingw targeted gcc+binutils living in /usr/i686-pc-mingw/[bin|include|lib|share] > I like /usr/cross, myself, so you could have /usr/cross/i686-pc-mingw, > /usr/cross/arm-v4l-linux, etc. I'm impartial on this, but I wonder... what does the LSB and SFH (or whatever the layout standard is called) recommend for this? Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
