Previous Thread
Next Thread
Print Thread
Page 31 of 42 1 2 29 30 31 32 33 41 42
Joined: Aug 2015
Posts: 392
Senior Member
Offline
Senior Member
Joined: Aug 2015
Posts: 392
RB: Thanks for the tip! :-)

For the interested reader I can point out that the layout_filename really IS the unquoted symbolname created by concatenating "layout_" and the prefix of the layout filename, in my case layout_mp68a and layout_md6802. The symbol is created by the make system by parsing the layout file into the .lh file. There is no compile error trying a string or some other ignorance. The next thing to lookout for is the -debug switch that seems to block the late binding of the 7seg IF more than one machine driver is provided in the build and the selection menu appears. Then you need to explicit say which driver to debug on the command line, for example:

Code:
./didact64d mp68a -window -debug


Because I can
Joined: Mar 2001
Posts: 16,834
Likes: 43
R
Very Senior Member
Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,834
Likes: 43
Yeah. Single-driver builds are more accurately single-driver file builds; you get all the drivers in the driver .cpp so you still have to specify the game name on the command line.

Joined: Nov 2010
Posts: 92
Likes: 1
Member
Offline
Member
Joined: Nov 2010
Posts: 92
Likes: 1
sorry for my ignorance but ...

i got a

'head' n'est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
GCC 4.9.1 detected
Building configurations...

...

makefile:830: recipe for target 'windows_x64' failed
make: *** [windows_x64] Error 2

with mingw env

my last good compilation is from 3 january 2016

can someone tell me what i can change to compil again ;-)

thanks in advance

Joined: Mar 2001
Posts: 16,834
Likes: 43
R
Very Senior Member
Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,834
Likes: 43
You aren't using the latest Windows tools, which are GCC 5.3.1.

Joined: Jan 2012
Posts: 877
Likes: 7
C
Senior Member
Offline
Senior Member
C
Joined: Jan 2012
Posts: 877
Likes: 7
Even with the newest tools I've found win32 make sometimes fails for no reason. If there was no other error just try running make again and see if it finishes.

Joined: Nov 2010
Posts: 92
Likes: 1
Member
Offline
Member
Joined: Nov 2010
Posts: 92
Likes: 1
hi

thanks for the reply

i'd go from mingw to msys64, after some path tweak of my batch, compilation work again ;-)

i have sometime also make errors but retry and pass like crazyc

thanks a lot !!!

Joined: Aug 2012
Posts: 67
Member
Offline
Member
Joined: Aug 2012
Posts: 67
I'm also having trouble compiling.
I get the following with the current build tools:

Code:
make -j9 USE_NETWORK=1 sse4=1 PTR64=1 NOWERROR=1


Code:
../../../../../src/emu/luaengine.cpp: In member function 'void lua_engine::start_console()':
../../../../../src/emu/luaengine.cpp:1026:2: error: 'thread' is not a member of 'std'
  std::thread th(::serve_lua, this);
  ^
../../../../../src/emu/luaengine.cpp:1027:2: error: 'th' was not declared in this scope
  th.detach();
  ^
../../../../../src/emu/luaengine.cpp: At global scope:
../../../../../src/emu/luaengine.cpp:864:14: warning: 'void* serve_lua(void*)' defined but not used [-Wunused-function]
 static void *serve_lua(void *param)
              ^
make[2]: *** [../../../../mingw-gcc/obj/x64/Release/src/emu/luaengine.o] Error 1
make[1]: *** [emu] Error 2


Near the beginning I notice this:

Code:
emu.make:1286: recipe for target '../../../../mingw-gcc/obj/x64/Release/src/emu/luaengine.o' failed

Joined: Aug 2012
Posts: 67
Member
Offline
Member
Joined: Aug 2012
Posts: 67
bump

Joined: Jun 2001
Posts: 61
O
Member
Offline
Member
O
Joined: Jun 2001
Posts: 61
you have outdated build tools. Download the latest from https://github.com/mamedev/buildtools

Joined: Aug 2012
Posts: 67
Member
Offline
Member
Joined: Aug 2012
Posts: 67
Using the commandline:

Code:
make -j9 NOWERROR=1 PTR64=1 sse4=1 USE_NETWORK=1


I get the following when it tries to link the executable:

Code:
Linking mame64.exe...
../../../../mingw-gcc/bin/x64/Release/mame_mame/libseibu.a: file not recognized: File format not recognized
collect2.exe: error: ld returned 1 exit status
mame.make:228: recipe for target '../../../../../mame64.exe' failed
make[2]: *** [../../../../../mame64.exe] Error 1
Makefile:952: recipe for target 'mame' failed
make[1]: *** [mame] Error 2
makefile:847: recipe for target 'windows_x64' failed
make: *** [windows_x64] Error 2


Any ideas?

Page 31 of 42 1 2 29 30 31 32 33 41 42

Link Copied to Clipboard
Who's Online Now
0 members (), 31 guests, and 6 robots.
Key: Admin, Global Mod, Mod
ShoutChat
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Forum Statistics
Forums9
Topics8,990
Posts118,128
Members5,005
Most Online890
Jan 17th, 2020
Forum Host
These forums are hosted by www.retrogamesformac.com
Forum hosted by www.retrogamesformac.com