Home Page Forums MAME MAME Can't compile latest MAME? READ THIS THREAD

I'm trying to compile the latest version of MESS (r15639) and keep getting a MegaCD error. I've deleted the both the OBJ and SRC folders, but I'm still getting the same error message. I'm not sure what to do.

try "make depend" and then attempt another make

you shouldn't have to tho, sounds like the dependencies weren't added correctly in the makefile

The -Wno-narrowing means a non-MAMEdev GCC 4.7.0 or later is in the $(PATH), and at that point all other errors are to be ignored.

I appreciate the efforts here. I tried make depend, but it hasn't made a difference unfortunately. I'm using the latest version of TortoiseSVN and mingw-mame-w64-20110519.exe (found here: http://mamedev.org/tools/) on Windows 7 Home Premium 64-Bit.

Do I need to update mingw64? I had attempted to do this from here (http://sourceforge.net/projects/mingw-w64/files/mingw-w64/mingw-w64-release/) although I think I downloaded the v1.0.4 instead of v2.0.4, but inside v1.0.4 there was no bin folder with make.exe etc... So I'm not sure what to download other than what is on the mamedev website. I guess I can try and download the revision before the MegaCD changes were made and see if I can compile the source, but I'm not sure what to do if releases after that won't compile.

Hello,

I have updated my daily build site with the new development tools (mingw-mame-w32-20120807.exe) and I have this error when doing "c:\mingw\mingw64-w32\bin\make TARGET=mess" :

Compiling src/osd/windows/vconv.c...
cc1.exe: internal compiler error: Illegal instruction
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make: *** [obj/windows/osd/windows/vconv.o] Error 1


vconv.c is the very first file trying to be compiled. So in fact cc1.exe does not work at all.

The daily build machine is WinXP 32 bits.

Does it ring a bell for any of you ?

Since you're calling "make" with its full path, are you sure that the cc1.exe being called is the right one? I mean, did you change your %PATH% env. variable to point to the new tools' binaries?

I cannot reproduce this here on Windows 7 (x64) at least, using the 32-bit version of the new tools...

Yes I have updated the PATH to point to c:\mingw\mingw64-w32\bin

I used to use full path in my script for some historical reason (I do not recall why exactly). I guess it's not usefull anymore and I could remove this.
I think I have tested without full path yesterday, but I will double check when back home.

OK, just for reference... this is how I setup my environment, having installed the 32-bit tools in 'c:\mingw64-w32':

Note that there are two required paths.

Oh ! I didn't do that.
I only set the first one since this is what is written on mamedev page. I will try this tonight thanks.