Unable to compile MAMEUIFX since .156

[lamouettasse]

Hi everybody, until then I successfuly compiled my own flavour of MAMEUIFX64+no nag .diff. Until then because now it won't compile.

When the compilation starts the first lines I'm granted are:

process_begin: CreateProcess(NULL, gcc --version, ...) failed.
make: makefile:142: pipe: No error
process_begin: CreateProcess(NULL, gcc --version, ...) failed.
make: src/build/cc_detection.mak:10: pipe: No error
process_begin: CreateProcess(NULL, gcc --version, ...) failed.
make: src/build/flags_gcc.mak:2: pipe: No error
process_begin: CreateProcess(NULL, gcc --version, ...) failed.
make: src/osd/winui/winui.mak:106: pipe: No error


Then compilation starts as usual and crashes within 10s, giving me that awful undecipherable (at least to me) error code:

process_begin: CreateProcess(NULL, gcc -DCRLF=3 "-DINLINE=static inline" -DLSB_F
IRST -DNDEBUG -DUSE_NETWORK -DFLAC__NO_DLL -DX64_WINDOWS_ABI -DUSE_QTDEBUG=0 -DU
SE_SDL=0 -DUNICODE -D_UNICODE -DNATIVE_DRC=drcbe_x86 -pipe -Wno-deprecated-decla
rations -O3 -Werror -fno-strict-aliasing -march=core2 -msse4.2 -Wno-unknown-prag
mas -Wall -Wcast-align -Wundef -Wformat-security -Wwrite-strings -Wno-sign-compa
re -Wno-conversion -include src/osd/windows/winprefix.h -DDIRECTINPUT_VERSION=0x
0700 -Isrc/mame -Iobj/winui/mame/layout -Isrc/emu -Iobj/winui/emu -Iobj/winui/em
u/layout -Isrc/lib/util -Isrc/lib -Isrc/osd -Isrc/osd/winui -Isrc/lib/expat -Isr
c/lib/zlib -Isrc/lib/util -Isrc/lib/libjpeg -Isrc/lib/portmidi -Isrc/osd/windows
 -Isrc/lib/winpcap -x c++ -std=gnu++98 -Woverloaded-virtual -DDIRECT3D_VERSION=0
x0900 -c src/build/makedep.c -o obj/winui/build/makedep.o, ...) failed.
make (e=2): Le fichier spÚcifiÚ est introuvable.
makefile:947: recipe for target 'obj/winui/build/makedep.o' failed
make: *** [obj/winui/build/makedep.o] Error 2
make: *** Waiting for unfinished jobs....
process_begin: CreateProcess(NULL, gcc -DCRLF=3 "-DINLINE=static inline" -DLSB_F
IRST -DNDEBUG -DUSE_NETWORK -DFLAC__NO_DLL -DX64_WINDOWS_ABI -DUSE_QTDEBUG=0 -DU
SE_SDL=0 -DUNICODE -D_UNICODE -DNATIVE_DRC=drcbe_x86 -pipe -Wno-deprecated-decla
rations -O3 -Werror -fno-strict-aliasing -march=core2 -msse4.2 -Wno-unknown-prag
mas -Wall -Wcast-align -Wundef -Wformat-security -Wwrite-strings -Wno-sign-compa
re -Wno-conversion -include src/osd/windows/winprefix.h -DDIRECTINPUT_VERSION=0x
0700 -Isrc/mame -Iobj/winui/mame/layout -Isrc/emu -Iobj/winui/emu -Iobj/winui/em
u/layout -Isrc/lib/util -Isrc/lib -Isrc/osd -Isrc/osd/winui -Isrc/lib/expat -Isr
c/lib/zlib -Isrc/lib/util -Isrc/lib/libjpeg -Isrc/lib/portmidi -Isrc/osd/windows
 -Isrc/lib/winpcap -x c++ -std=gnu++98 -Woverloaded-virtual -DDIRECT3D_VERSION=0
x0900 -c src/lib/util/astring.c -o obj/winui/lib/util/astring.o, ...) failed.
make (e=2): Le fichier spÚcifiÚ est introuvable.
makefile:947: recipe for target 'obj/winui/lib/util/astring.o' failed
make: *** [obj/winui/lib/util/astring.o] Error 2
Generating XML file...

I thought I might have a problem with my mingw environment so I downloaded it again, reinstalled it and manually ensured the variable path was set (variable= path ; value=I:\mingw\mingw64-w64\bin;mingw\mingw64-w64\opt\bin;mingw\mingw64-w64\Qt\bin;)

Does someone have any clue about the step I miserably fail without even realising? Any help would be greatly appreciated and by the way happy new year to all of you.

[haynor666]

Compliles fine on windows 7 x64 and latest MinGW. I only set only variables in PATH: C:\Windows\MinGW\bin;c:\Windows\MinGW\opt\bin\
Problem might be with your custom no nag patch.

[lamouettasse]

Yeah, I thought about that too and tried without it in the first place, no changes. For the sake of clarity I must say that if I'm no dev I succesfully compiled MAME for more than a year and never hit a brickwall like that. Just did everything by the book several times, the problem doesn't lay in the sources but is clearly mingw related. After all the first error message I'm granted with when I start compiling seems clear about that.

I use the latest tools, use the batches included (setenv.bat and his friends), type in the necessary command to set the environment variables but it simply doesn't work. More troubling is the fact that I can't find a reference to mingw in my OS variables environment. There should be one right? Well it's simply not created, so I have to create this entry manually I guess but what should I type in? Variable: path that part is ok, the other one is more complicated to me. I guess the value I'm gonna type in needs to be given the whole path to mingw? Could someone clarify that to me?

One more troubling thing is the fact that I succesfully compiled MAMEUIFX64 .156 and there have been no changes in the dev tools or in my environment in between (for this last part, at least nothing that I'm aware of) .156 and .157. So what the ---fudgesicle---?

I guess I badly need a mingw guru or a compilation ninja or something in the like.

[haynor666]

You could remove all sources, remove MinGW and entry in PATH. Restart computer, download mingw (only 64bit) from mamedev site. Extract it for example to C:\MinGW and add variables into PATH (just 2 mentioned) download again source then copy mameuifx source over official one and make file compile.cmd with those lines

Code: [Select]

MAKE -j4 OSD=winui PTR64=1
pause
For unknown reason sometimes compiling fails also on my computer and until I restart computer it fails all the time (buffer???).

[lamouettasse]

I did what you said and sadly it didn't change the situation. I've been fighting this for days and have made no progresses so far. My next move is gonna be drastic: I'll wipe my computer clean and have a fresh start. Something has changed in my computer since .156 and I don't know what. Mingw is correctly installed, mame source trees are perfectly laid out so I'm out of option. Thanks for your time Haynor666, I hope I'll be able to report a success soon.

[haynor666]

How about fresh install in VirtualBox first.

[lamouettasse]

 This is an excellent suggestion, thanks for bringing that up! I have a vmware installer that's been sitting in my hdd for 6 months, it's time to fire it up. I'll keep you updated.

[lamouettasse]

Well your idea works flawlessly, a tiny bit slow maybe but I don't care as long as it works. Thanks for your time and your great suggestion.