compiling problems

[gazz292]

i'm having a go at compiling mame for the first time ever, using headkaze's mame compiler 64,

i followed the instructions, making the required folders, got the source for mame 0140, the hi-score patch for mame 0140 as a text file, renamed to a .diff file as instructed, applied the patch, set it to compile for a pentium 4 (+sse3), only box ticked was 'clean compile' and hit go (using XP 32 bit with sp3 installed)

39 minutes later is messes up with the following error:

src/osd/windows/video.c: In function 'void osd_update_hi(running_machine*, int)':
src/osd/windows/video.c:264: error: redefinition of 'void osd_update_hi(running_machine*, int)'
Finished!
0 Hours 39 Minutes and 25 Seconds Elapsed.
src/osd/windows/video.c:240: error: 'void osd_update_hi(running_machine*, int)' previously defined here
src/osd/windows/video.c: In function 'void osd_update_hi(running_machine*, int)':
src/osd/windows/video.c:288: error: redefinition of 'void osd_update_hi(running_machine*, int)'
src/osd/windows/video.c:240: error: 'void osd_update_hi(running_machine*, int)' previously defined here
src/osd/windows/video.c: In function 'void osd_update_hi(running_machine*, int)':
src/osd/windows/video.c:312: error: redefinition of 'void osd_update_hi(running_machine*, int)'
src/osd/windows/video.c:240: error: 'void osd_update_hi(running_machine*, int)' previously defined here
src/osd/windows/video.c: In function 'void osd_update_hi(running_machine*, int)':
src/osd/windows/video.c:336: error: redefinition of 'void osd_update_hi(running_machine*, int)'
src/osd/windows/video.c:240: error: 'void osd_update_hi(running_machine*, int)' previously defined here
src/osd/windows/video.c: In function 'void osd_update_hi(running_machine*, int)':
src/osd/windows/video.c:360: error: redefinition of 'void osd_update_hi(running_machine*, int)'
src/osd/windows/video.c:240: error: 'void osd_update_hi(running_machine*, int)' previously defined here
make: *** [obj/windows/mame/osd/windows/video.o] Error 1

Any ideas what has gone wrong? is the _hi bit refering to the hi-score patch, but i see video mentioned.

i'm really out of my depth here, i've tried compiling it twice, and got the same error.

any pointers gratefully recieved.

[Pingaloka]

Try to compile setting "optimize for" to none, in compile options.

[gazz292]

okiedokie will do,

does it look like that's whats causing the problem from the error messages?

i wish i could make sense of them, i am thinking they are to do with resolutions for the video card.... mentions of 240, 288, 312 etc, they sound like part or resolutions listed for my avga card,

[gazz292]

nope, something buggered up,

tried compiling with 'optimize for' set to 'none'

this time it took 8 seconds, first thing it showed was 'compiling src/osd/windows/video.c...'
and then it shows the errors listed above,

i guess i've got a corrupted source file, or the patch is messing things up... or something???

[Pingaloka]

Try what ive'd told you, but start from the beggining.
Erase your MAME source files as they may be already corrupt, download MAME0140 source files again,
download patch 0.140 Highscore.diff again, as it was modified yesterday by MKChamp.
Open compiler, apply patch, and try compiling with all boxes unchecked, and "Optimize for" in "non" option.
Let's see what happens.

[gazz292]

just done what you said, deleted the mame source files and hiscore file, downloaded them fresh,

compiled with no tick boxes or owt, and got this:

src/osd/windows/video.c: In function 'void osd_update_hi(running_machine*, int)':
src/osd/windows/video.c:264: error: redefinition of 'void osd_update_hi(running_machine*, int)'
Finished!
0 Hours 39 Minutes and 13 Seconds Elapsed.
src/osd/windows/video.c:240: error: 'void osd_update_hi(running_machine*, int)' previously defined here
make: *** [obj/windows/mame/osd/windows/video.o] Error 1

[dna disturber]

just done what you said, deleted the mame source files and hiscore file, downloaded them fresh,

compiled with no tick boxes or owt, and got this:

src/osd/windows/video.c: In function 'void osd_update_hi(running_machine*, int)':
src/osd/windows/video.c:264: error: redefinition of 'void osd_update_hi(running_machine*, int)'
Finished!
0 Hours 39 Minutes and 13 Seconds Elapsed.
src/osd/windows/video.c:240: error: 'void osd_update_hi(running_machine*, int)' previously defined here
make: *** [obj/windows/mame/osd/windows/video.o] Error 1

Same here.......looked all over the forum since I didn't compile mame since 0.130 I thought I must be doing something wrong.   (tried it like 5 times already but everytime the same outcome).....one thing I haven't tried is another computer..
I'm using mamecompiler v1.20
My computer AMD64 x2 dual using xp32 sp3

dna disturber  

[gazz292]

i'm having another go at compiling it, deleted everything even the compiler proggy, re-downloaded it all, but this time i downloaded the .exe version of mame rather than the .zip version, from what i can tell theres no differance, just the .exe is a windowz self extracting file.

it's currently churning through it, but i'm not holding my breath,
wish i knew what the errors ment, is it something to do with the hiscore diff, or the video modes,

[gazz292]

New problem,

it ran for just over an hour, and then i got a windows popup telling me that 'png2bdc.exe has encountered a problem and needs to close'

telling it not to send the damn error repotr closes the popup, and the compile failes with "make: ***[obj/windows/mame/emu/uismall.fh] Error - 1073741819

   

danmit, what am i doing wrong.

[dna disturber]

Did it on another computer and it worked like a charm.... 
Maybe you could try it also on another computer. 

dna disturber 

[gazz292]

it is annoying i cant get it to work, i just wish i could decipher the fail codes,

i'm going to have a go at compiling manually as mentioned on the mame devs page, tho i am wondering how to add the hi-score patch, it only mentions adding the u patches,

i downloaded a pre-compiled version of mame 0140 with the hi-score patch applies, but it wont run on my system, which i read about, lots of people having probs running compiled versions on other computers than they were origionaly compiled for.

[Pingaloka]

If you can't get it to work, tell me and I'll send you a copy of my compiled version via private message.

[gazz292]

i am not having much luck,

i tried to compile it the manual way according to mr do's site, couldent even manage that, it wont even accept the 'mamemame' command, managed to apply the hi_140.diff patch tho,

i dunno, maybe something is missing on my computer,

i wanted to compile my own mame firstly to get rid of the nag screens, but also to optimize it for my processor,
i tried someone elses compiled mame, but it wouldent work on my system.

[gazz292]

i'm amazed... i was ready to give up, but i thought i'd try one last time....

i deleted everything to do with mame off the computer except the roms and things like cabinets, marquees and so on, moved them to a new folder out of the way,

re-downloaded everything needed to compile, applied the patch and hit go, then jumped into bed with the GF, hours and hours of passionate love making later i came back to check on its progress, but it was still compiling, the clock thing must be wrong as it said it had only been running for 2 minutes, but i was at it for hours, honnest 

honnestly tho, i went in expecting to see the red text telling me it had failed again, but it was showing 'finished', at 1 hour 2 minutes no less, and it had brought up the folder view of the resulting mame.exe file.

so i fired up mala, pointed it at the new mame compile, and selected a game, and she bloomin well worked, no nag screens and high scores being saved, 

I had the tick boxes set all off except for the dual core one, that one is always ticked when i start MC64, the processor i have is a hyperthreading one not a true dual core, but i thought i'd leave it ticked this time (last few times i had every tick box off)

i'm now trying another compile with the 'optimize for : pentium 4 +sse' selected, as i believe that's my processor (P4 prescot, 3.06 gig) but i dont expect this to work, as i read lots of posts on other forums about any optimizations fail with that 'png2bdc' error.

[MKChamp]

i'm amazed... i was ready to give up, but i thought i'd try one last time....

i deleted everything to do with mame off the computer except the roms and things like cabinets, marquees and so on, moved them to a new folder out of the way,

re-downloaded everything needed to compile, applied the patch and hit go, then jumped into bed with the GF, hours and hours of passionate love making later i came back to check on its progress, but it was still compiling, the clock thing must be wrong as it said it had only been running for 2 minutes, but i was at it for hours, honnest 

honnestly tho, i went in expecting to see the red text telling me it had failed again, but it was showing 'finished', at 1 hour 2 minutes no less, and it had brought up the folder view of the resulting mame.exe file.

so i fired up mala, pointed it at the new mame compile, and selected a game, and she bloomin well worked, no nag screens and high scores being saved, 

I had the tick boxes set all off except for the dual core one, that one is always ticked when i start MC64, the processor i have is a hyperthreading one not a true dual core, but i thought i'd leave it ticked this time (last few times i had every tick box off)

i'm now trying another compile with the 'optimize for : pentium 4 +sse' selected, as i believe that's my processor (P4 prescot, 3.06 gig) but i dont expect this to work, as i read lots of posts on other forums about any optimizations fail with that 'png2bdc' error.

Haha...I got a kick out of this post. I'm sure you compiled three or four times in one night, too! At my age(37), I'm good for one at most....and I don't wait for the GF either :-)

[gazz292]

lol, i'm 33 so making the most of it while it lasts 

no luck with compiling for my processor, got the png2bdc error again, seems thats what most people get when trying to compile for a specific processor,
bloody annoying as i want to get the most out of this computer i can, so thought compiling for my specific hardware would be the best thing to do,

everywhere i read, that png2bdc thing is part of mame and not the compiler, so not much hope of it being fixed, when mame works unless you mess with it trying to customize it.

[headkaze]

bloody annoying as i want to get the most out of this computer i can, so thought compiling for my specific hardware would be the best thing to do

Does auto detect work? According to Aaron Giles it doesn't make a whole lot of difference to compile an optimized binary anyway.

[gazz292]

nope, anything but a non optimized build fails with the png2bdc thing.

i'll just live with it as it is i guess i've managed to get it with the no nag and hi-score patches added, so that's the main thing,

next is to remove all the crap windows has that i dont need.... watch out for my next post titles 'i've borked my OS'