> > I've tried to rebuild a number of programs I have written using GCC 3.3.3 > and > every single one of them seem to work as they should. Many of them are > Win32 > GUI programs (written in C++), some are programs using posix functions. > > So my question is: What problems can I expect if continue to use GCC > 3.3.3?
Other then dealing with non-standard install locations (probably leading to the c++ issue you had), and probably missing cygwin-specific features there shouldn’t be any 'problems'. An example of something likely to be missing is -mno-cygwin. > Should I go back to GCC 3.3.1 or is it fine to continue to use the later > version? Any other drawbacks of this upgrade? Any benefits? If someone > would > shed some light on this I would be grateful. Given you have installed in a separate location it is not like you have any problems here, you can use the installed gcc 3.3.1 when you need it - and your own built 3.3.3 when you need that. You haven’t 'upgraded' as such just installed a newer version as well. But given that you don’t know why you've installed it, perhaps you just shouldn’t bother with it. 3.3.3 is mostly a bug fix release relative to 3.3.1 - go visit gcc.gnu.org to find out what bug fixes have occurred. Now if you haven’t experienced the bugs, then there is probably no point for you to have a custom build and you should just wait for whenever the cygwin gcc maintainer updates the cygwin gcc distribution. However if a bit of research finds that 3.3.3 has something you want then by all means, use it - we're not going to stop you. ... Well okay, I'm not going to stop you. Gareth -- 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/
