MAMEWorld Forums - Programming - Re: Compiling problems with MAME64

> Not sure if this is the best place to put this, but I've been compiling my own
> versions from source code for years.
>
> No changes to the compiling environment has taken place recently, and the 156 code
> compiled just fine.
>
> But when I compile 157, I get this:
>
> Compiling src/osd/windows/vconv.c...
> Compiling src/build/makedep.c...
> Compiling src/lib/util/astring.c...
> Compiling src/lib/util/corealloc.c...
> Compiling src/lib/util/corefile.c...
> src/lib/util/corealloc.c: In static member function 'static memory_entry*
> memory_entry::allocate(size_t, void*, const char*, int, bool)':
> src/lib/util/corealloc.c43: error: cast from 'void*' to 'FPTR {aka unsigned int}'
> loses precision [-fpermissive]
> src/lib/util/corealloc.c: In static member function 'static memory_entry*
> memory_entry::find(void*)':
> src/lib/util/corealloc.c42: error: cast from 'void*' to 'FPTR {aka unsigned int}'
> loses precision [-fpermissive]
> src/lib/util/corealloc.c: In static member function 'static void
> memory_entry::release(memory_entry*, const char*, int)':
> src/lib/util/corealloc.c52: error: cast from 'void*' to 'FPTR {aka unsigned int}'
> loses precision [-fpermissive]
> make: *** [obj/windows/lib/util/corealloc.o] Error 1
> make: *** Waiting for unfinished jobs....
>
> The 32-bit version compiled just fine in that environment, but my 64-bit environment
> is blowing up as soon as the compiling begins.
>
> Is anyone else having this problem, or know what may be going on?
>
> thanks.

You are using a GCC/MingW version dissimilar to the current baseline tools (baseline uses 4.9.1), so the --version string the makefile uses to detect your compile environ isn't detecting yours properly for 64-bit. For now, you need to add "PTR64=1" to your make command for proper 64-bit compiling.