|
Compiling problems with MAME64
#335607 - 01/01/15 09:24 AM
|
|
|
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:
Code:
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.c:294:43: 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.c:319:42: 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.c:342:52: 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.
|
|
|
Tafoid |
|
I keep on testing.. testing.. testing... into the future!
|
|
|
|
|
Reged: 04/19/06
|
|
Posts: 3135
|
|
Loc: USA
|
|
|
|
Send PM
|
|
|
Re: Compiling problems with MAME64
[Re: Llaffer]
#335615 - 01/01/15 01:46 PM
|
|
|
> 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.
|
|
|
|
Re: Compiling problems with MAME64
[Re: Tafoid]
#335621 - 01/01/15 06:33 PM
|
|
|
hmm. When did that update? I'll see if I can update the tools and try again.
|
|
|
| redk9258 |
|
Regular
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 3968
|
|
Loc: Troy, Illinois USA
|
|
|
|
Send PM
|
|
|
Re: Compiling problems with MAME64
[Re: Llaffer]
#335622 - 01/01/15 06:44 PM
|
|
|
|
|
|
Re: Compiling problems with MAME64
[Re: redk9258]
#335623 - 01/01/15 06:53 PM
|
|
|
I somehow completely missed that.
I compile my 32-bit version on another machine that has the 32-bit version of MING installed on it and it worked just fine. So strange how I have to update one and not the other.
Not that I'm not agreeing with your statement, I would have expected it to fail in both. I will update my 32-bit machine when I have access to it (it's a shared machine with my kids, where my 64-bit compiling machine is mine and mine alone.)
|
|
|
|
Re: Compiling problems with MAME64
[Re: Tafoid]
#335624 - 01/01/15 07:06 PM
|
|
|
Here is what I'm getting now:
I've updated to the 4.9.1 compiler:
Code:
G:\src\mame>gcc --version
gcc (x86_64-win32-seh-rev0, Built by MinGW-W64 project) 4.9.1
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I've added the code you recommended in my compiling batch file:
Code:
echo Compiling ...
make -j5 PTR64=1
and it gets further, but still blows up pretty early:
Code:
mkdir.exe -p obj/windows64/osd/modules/debugger
mkdir.exe -p obj/windows64/osd/modules/sound
mkdir.exe -p obj/windows64/osd/windows
mkdir.exe -p obj/windows64/tools
Compiling src/lib/util/astring.c...
Compiling src/lib/util/corefile.c...
Compiling src/lib/util/corealloc.c...
Compiling src/build/makedep.c...
Compiling src/osd/windows/vconv.c...
Assembler messages:
Fatal error: can't create obj/windows64/build/makedep.o: No such file or directory
Compiling src/lib/util/unicode.c...
Compiling src/lib/util/tagmap.c...
src/build/makedep.c:463:1: fatal error: error writing to -: Invalid argument
}
^
compilation terminated.
makefile:947: recipe for target 'obj/windows64/build/makedep.o' failed
make: *** [obj/windows64/build/makedep.o] Error 1
make: *** Waiting for unfinished jobs....
Any other thoughts?
|
|
|
|
Re: Compiling problems with MAME64
[Re: Llaffer]
#335626 - 01/01/15 07:15 PM
|
|
|
Well, that's weird.
I ran my batch file again (which always deletes the source and then recopies a fresh copy of the source from an alternate directory), and it's compiling now.
When this is done, I'll test the full compiling script with includes MAME64 and MAMEUI64.
Thanks for your help.
|
|
|
|
Re: Compiling problems with MAME64
[Re: Llaffer]
#335627 - 01/01/15 07:32 PM
|
|
|
For some reason I'm also having compilation problems with mame64. When I try to compile,it says it needs the layout files to continue. These layout files aren't in the source.
Edited by coltonmameworld (01/01/15 07:32 PM)
|
|
|
| redk9258 |
|
Regular
|
|
|
|
|
|
Reged: 09/21/03
|
|
Posts: 3968
|
|
Loc: Troy, Illinois USA
|
|
|
|
Send PM
|
|
|
Re: Compiling problems with MAME64
[Re: coltonmameworld]
#335648 - 01/02/15 03:34 AM
|
|
|
> For some reason I'm also having compilation problems with mame64. When I try to
> compile,it says it needs the layout files to continue. These layout files aren't in
> the source.
Can you start your own thread and describe the exact steps you follow when compiling?
|
|
|
Index 
Threaded 
Compiling problems with MAME64
Reply
[Re: 
