Viewing Issue Advanced Details
|ID||Category [?]||Severity [?]||Reproducibility||Date Submitted||Last Update|
|07577||Compiling||Minor||Always||Feb 29, 2020, 10:03||Feb 29, 2020, 11:34|
|Tester||EoceneMiacid||View Status||Public||Platform||MAME (Self-compiled)|
|Assigned To||Resolution||Invalid report||OS||Linux (64-bit)|
|Version||0.218||Fixed in Version||Build||64-bit|
|Fixed in Git Commit||Github Pull Request #|
|Summary||07577: naomi: Unable to compile 0.219 tinybuild with Naomi driver inlcuded|
0.219 isn't in the version dropdown box yet. I'll update the report once it is.
Compiling a tinybuild with the Naomi driver included generates the following error while linking:
/usr/bin/ld: ../../../../linux_gcc/bin/x64/Release/mame_tinymame/libmame_tinymame.a(gunsense.o): in function `sega_gunsense_board_device::device_add_mconfig(machine_config&)':
gunsense.cpp:(.text+0xc1): undefined reference to `upd78213_device::upd78213_device(machine_config const&, char const*, device_t*, unsigned int)'
collect2: error: ld returned 1 exit status
make: *** [tinymame.make:269: ../../../../../tinymame64] Error 1
make: *** [Makefile:103: tinymame] Error 2
make: *** [makefile:1345: linux_x64] Error
Without the Naomi driver, my build compiles just fine.
|Steps To Reproduce||
Compile a tinybuild with the Naomi driver included e.g.
make SUBTARGET=tinymame USE_QTDEBUG=0 SOURCES=src/mame/driver/naomi.cpp REGENIE=1 NOWERROR=1 LDOPTS=-Wl,--start-group -j9
|Affected Sets / Systems||naomi|
|There are no relationship linked to this issue.|
Feb 29, 2020, 11:00
There was an error in cpu.lua, is it fixed with this?
Feb 29, 2020, 11:05
edited on: Feb 29, 2020, 11:09
you should delete all files in /linux_gcc/bin/x64/Release/mame_tinymame/ and then build again.
technically it is flaw in current build system: in the case of new devices addition to some driver there needed to manually clean .a files in /Release/mame_xxxxxx/
Feb 29, 2020, 11:34
|SUBTARGET=tiny is tested for tagged releases, we don’t test every possible SOURCES= and we don’t guarantee that they all work. You can work around it yourself, or submit a fix in a pull request. It's not a bug.|