07406: MAME 0.213 fails to compile under Linux 64 bit

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
07406	Compiling	Major	Always	Sep 5, 2019, 01:25	Sep 5, 2019, 15:12

Tester	MrGW	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Invalid report	OS	Linux (64-bit)
Status [?]	Closed			Driver
Version	0.213	Fixed in Version		Build	64-bit
		Fixed in Git Commit		Github Pull Request #

Summary	07406: MAME 0.213 fails to compile under Linux 64 bit
Description	I have had no issues compiling MAME for the last 3 years, but getting a compile error with 0.213 as detailed in attached text.
Steps To Reproduce	Download latest MAME source from git. make TOOLS=1 NOWERROR=1 ... takes some time and then the error.
Additional Information	$ gcc --version gcc (Ubuntu 8.3.0-16ubuntu3~16.04) 8.3.0 Copyright (C) 2018 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. $ g++ --version g++ (Ubuntu 8.3.0-16ubuntu3~16.04) 8.3.0 Copyright (C) 2018 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. $ ldd --version ldd (Ubuntu GLIBC 2.23-0ubuntu11) 2.23 Copyright (C) 2016 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. Written by Roland McGrath and Ulrich Drepper. Thanks for any help someone can provide.
Github Commit

Flags
Regression Version
Affected Sets / Systems

Attached Files	compilerrror.txt (2,810 bytes) Sep 5, 2019, 02:05 Uploaded by Tafoid compile error text [Show Content]

No.16835 Tafoid Administrator Sep 5, 2019, 03:03	Are you 100% positive you are using the mamedev.org provided sources and/or pulling from branch "mame0213"? https://github.com/mamedev/mame/tree/mame0213
No.16836 MrGW Tester Sep 5, 2019, 12:39	Hi Tafoid, Yes, I believe so: $ git branch -a * mame0213 master remotes/origin/3rdparty_update remotes/origin/HEAD -> origin/master remotes/origin/android-updates remotes/origin/argb32_all remotes/origin/arm_playground remotes/origin/c148_rewrite remotes/origin/cashier-knife remotes/origin/doxygen remotes/origin/floppy_sound remotes/origin/hlsl_aviplay remotes/origin/konami remotes/origin/ksys573_io remotes/origin/list_xml_light remotes/origin/lua_engine_ui_refactor_2 remotes/origin/macro_removal remotes/origin/make_coco_fdc_fixed remotes/origin/master remotes/origin/midtunit_video remotes/origin/n64-angrylion remotes/origin/netlist_dev remotes/origin/new_menus remotes/origin/optionalsplit remotes/origin/palmhacks remotes/origin/polyplay remotes/origin/precompiled_headers remotes/origin/psx_metafix remotes/origin/s32_kokoroji remotes/origin/saturn_cdblock remotes/origin/selfregister-drivers remotes/origin/ui_colors_refactor remotes/origin/voodoo_directx11 remotes/origin/vrender0_3 remotes/origin/wof I cleared it all and tried again. Same issue. Previous version compiles fine. Thanks again for your help.
No.16838 MrGW Tester Sep 5, 2019, 14:56	One additional test. I used the following command to download MAME (taken from the MAME download website): git clone -b mame0213 --depth 1 https://github.com/mamedev/mame.git mame0213 This seems to have worked. No issues compiling. I can't figure out why downloading from git and changing to the correct branch (prior to compiling) results in the errors I listed as it always worked for me before. In any case, there doesn't appear to be an issue. I apologize for submitting the report. Thanks
No.16839 Tafoid Administrator Sep 5, 2019, 15:11	Sources pulled from current Git master sources can fail in certain configurations though much testing is done to try to avoid this. In your case, your sources you pulled were not from the MAME213 tag which goes through more than normal compile testing in multiple OS/Configs to ready for release. A few others have reported this compile issue and has already been fixed in current Git - so that should now function properly as well. Closing.