I am not sure mixing development environments is desirable from the auto-build point of view. One of the goal of those builds is to track down early bugs. If the devs suspect the build environment for each bugs reported with my site's binaries, it will be counter productive. The binaries must be as trust worthy as possible.
Oh boy! Yes my CPU is an Athlon XP 2500+ so that may be why gcc 4.6.3 won't work. My reason for not buying a new computer with Windows 7 or 8 is that there is not yet sufficient reason to do so.
Anna, what is the combination you referred to? Do you list that info on your site? I see instructions for compiling QMC2 but not MESS. At least what I see does not seem to be what I need to build MESS.
Last edited by Robert Gault; 12/21/1210:18 PM. Reason: more text
These combinations work for me. Just for info, I have an Intel Mobile Pentium 4-M processor. OS is WinXP Pro SP3 32-bit
Anna, To clarify the above, how do you mix and match this? Do you take part of the old mame gcc 4.4.7 and drop it into the current mame package? Do you install the above as separate entities? Just assume I'm clueless and provide a step by step process.
bobz: Thing is that we already need to support various GCC versions due to Linux and OSX support, so in general there should not be errors that are passing 4.6 or 4.7 and not working on 4.4 (we had some issue with Apple compiler beeing more restrictive but not mingw), so if you add Python support over 4.4.7 build process will run and things noticed not working there will not work on 4.6 or 4.7 too. Thing is we can't help much if Mingw have issues that compiler is not working on some environments, since they introduce their own bugs (like latest 4.7.x 32bit is having issues)