Doesn't build on macOS Catalina with latest xcode (see log here).

You must have mangled your source and removed the COPYING file.

Yeah, I normally delete files and folders I assume I don't need after downloading.

Working now, thanks for the help.

Seriously, are you trying to waste our fucking time reading your logs then? If the error says it can't find the COPYING file, and you deleted the file, don’t you think it might be a hint that you shouldn’t do that?

Seriously, if you search your log for the first "***" that make outputs to flag an error, you find this:


I am not going to pay any attention to any of your reports any more. If you break it, you get to keep the pieces.

I spend enough of my time making sure releases actually build, work to some extent, and are presentable. I don’t need to waste it “helping” people who go out of their way to break things. Seriously, how the fuck do you expect me to feel? Why is your first reaction to complain, rather than consider that deleting random files from the source probably isn’t a great idea?

Well, I did not complain, I just reported my situation. In the past, whenever I had problems compiling the source the eventual fix was always way over my understanding of the matter.

I apologise for my stupidity and would welcome if you'd just ignore my postings in the future. I prefer not getting any help than angering you and wasting your time. I really appreciate your work and that of all the others that contribute to MAME.

Really sorry

I'd strongly recommend you change your years-long behaviour and no longer do this, it will be easier for you in the long run.

These days, MAME is more than just sourcecode and binaries, there's scripts and shaders and things that people think "well this probably didn't change between releases" and choose not to overwrite, causing themselves problems.

We've had to counsel every MAME fork and port maintainer to always bundle the version of shaders matched to that version's release, for instance.

Of course, I've learnt my lesson.