Rick Mann wrote: > I've been able to build an xscale-elf-targeted GCC (and binutils and > newlib) on Mac OS X. Now I have to do the same thing on Cygwin (ugh), > and it doesn't work. "Doesn't work" is pretty vague, we need specifics. > One thing is that Cygwin has GCC 3.4, not 4.x. That should not matter at all. Ted Byers wrote: > Cygwin is ALWAYS well behind. Yes, yes, snipe away. It's easy to complain. But have you considered that there's perhaps a reason why we only ship 3.4 with Cygwin, a reason that's not rooted in us being lazy? Could it possibly be that gcc 4.x is not yet fully functional on Cygwin? Could it be that C++ and java exceptions are seriously broken due to lack of shared libgcc and shared libstdc++ and shared libjava? That we want to switch the platform over to Dwarf-2 from SJLJ but we aren't sure how this will work on a platform where we can't recompile the operating system, and where Dwarf-2 unwinding will thus fail in certain circumstances? Could it just possibly be that we have reasons for sticking with 3.4 that don't amount to "just haven't gotten around to it", that we would rather ship a compiler that works rather than one that falls on its ass if you try to throw an exception across a shared library? Can you please stop labeling Cygwin as gratuitously out of date for no good reason? Brian
