03012: Numerous compile segfaults and errors

ID	Category [?]	Severity [?]	Reproducibility	Date Submitted	Last Update
03012	Compiling	Major	Always	Mar 9, 2009, 11:39	Mar 10, 2009, 11:12

Tester	Robbbert	View Status	Public	Platform	MAME (Self-compiled)
Assigned To		Resolution	Unable to reproduce	OS	Windows XP/Vista 32-bit
Status [?]	Closed			Driver
Version	0.130	Fixed in Version		Build	Normal
		Fixed in Git Commit		Github Pull Request #

Summary	03012: Numerous compile segfaults and errors
Description	A totally clean environment, with the recommended build tools, produced many segfaults in the compiler. Once these were sorted, many more strange errors until it finally compiled. The segfaults were all caused by the inclusion of #include "driver.h" in various .h files, i suspect it caused a circular reference. After that, not surprisingly, many other errors occurred. These were fixed by adding #include "driver.h" in the proper place in the affected .c files. The last problem was another segfault, this time in x1_010.c - the struct in x1_010.h had to be moved to x1_010.c before at last a successful compilation. Most people, it seems, have upgraded their tools and probably have not experienced these errors. I prefer to stay with the official recommendation. Some of the files affected: rendlay.h, tms34010.h, 6821pia.h, scsi.h, tms57002.h, vdc.h, rendutil.h After that i lost count... there were many more...
Steps To Reproduce	brand new clean compile with official tools. Should segfault when compiling asteroid.c when it tries to include rendlay.h
Additional Information	I don't normally compile u-versions, but happened to notice the problem with 129u6. Didn't try troubleshooting.
Github Commit

Flags
Regression Version
Affected Sets / Systems

Attached Files

No.03931 Haze Senior Tester Mar 9, 2009, 11:53	are you sure it's not just your pc? afaik I'm using the recommended tools and haven't seen any of this.
No.03935 Mamesick Senior Tester Mar 9, 2009, 14:34	It's fine here with official MAMEDev tools and a fresh source.
No.03937 Twisty Senior Tester Mar 9, 2009, 15:16	No problem here either.
No.03941 Fujix Administrator Mar 9, 2009, 16:55	It doesn't repro for me either.
No.03943 galibert Developer Mar 10, 2009, 11:12	Sounds like a memory issue. I recommend a run of memtest86, seriously.