Problems building mame 0.148

[epetti]

This is my first time trying to build mame from the source so I'm sure I'm making a stupid mistake.  Any help would be appreciated.  I followed Mr. Do's web page:

- download and extract mingw environment
- download and extract 0.148 source code
- I downloaded makemame and patchmame just to make setting the environment automatic
- I downloaded two patches (bezel from CPWizard, and hiscore no nag, etc.)
- I tried both with and without running the patches to make sure it wasn't an issue with the patches.

It runs all the mkdirs, and then when it first starts compiling I get this error:

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

Any ideas?  For some reason I think the first time got further before it errored, but I can't get that far back in my log.  When I delete the obj directory and recompile now, this is the error I always get.

Thanks in advance for any help with this.

[404]

have you tried mame compiler?
http://www.headsoft.com.au/?category=mame&page=mc64

[epetti]

Yes.  Still no luck.

[Haze]

The current compile tools require certain CPU extensions in order to work, meaning they'll just fail on older systems even if the actual builds they produce work fine.  There is nothing you can do to fix that.  (the tools were upgraded because compiling with older ones was causing bugs in some drivers)

I think it is a design choice from the guys who make the toolchain, unless they simply enabled some optimization by mistake, but that seems unlikely.  This is beyond the control of Mamedev, we simply use what is available.

Due to the nature of your request I'll be providing no further help, and remind people that distributing any builds with such mods, to anybody, is seriously frowned upon.

[epetti]

Thanks for the info. Request withdrawn. I'm starting to get the picture that my computer my be just too old. But I'll probably end up just trying to use CPWizard running live and hope it doesn't cause much of a performance hit.