Another person reported the same problem. It wasn't going to change it if it was an isolated problem, but it seems like everyone with GCC 4 had the problem.Mannequin wrote: So, you've made it so that just a simple "make" will do for the people that can't use the GC code? So you have to use something like "make GC=true" or some-such?
May I ask your reasons for inverting it like this?
Not true, zloba and I have made sure it has worked the vast majority of the time for Linux users with bug reports and some bug fixes. Randy also periodically builds on MinGW, so if he doesn't change any of the platform dependant (not just MSVC dependant) stuff and builds it on GCC before the release, it'll almost certainly compile and run fine on Linux too.QBasicer wrote:Linux is great, if you know what you're doing. Managing a project that works on linux and windows is difficult. Don't expect SVN to work on an operating system other than what's being developed. I expect a linux version come out of a stable release not long after a windows release has been made.
My efforts have certainly had benefits for Windows users too. Randy and Graf tracked down all or almost all of the memory leaks and off-by-one errors that I found using valgrind (an extremely valuable memory checker tool that runs on a number of unix-likes but not Windows). Also, it lead Randy to find and fix some of the dreaded Vexing bugs.