Home Page Forums MAME Non-Windows MAME Support SDLMAME build failure on Ubuntu 18.10

That's funny because I thought I tried that but I guess I didn't do it correctly. It seems to have worked and resulted in a ~208 MB mame64 binary getting built. I also had to declare QT_SELECT, this is on an 8 core machine. Xubuntu 18.10 with gcc 8.2.0.


Thanks.

I installed Ubuntu 19.04 on a new system and got the wonderful problems with compiling with FORTIFY_SOURCE.

So now I just create an alias in my .bashrc

alias mmake='make CFLAGS="-U_FORTIFY_SOURCE" '

and then just type mmake instead of make.

Sorry for the necrothread reply, but I thought it was worth mentioning that with 0.253's new compiler requirements, I was able to successfully build MAME in Ubuntu 22.10 with plain make and no additional compiler flags enabled.

I’d be surprised if the increase in required libc++ version affects anyone. Most of the people using libc++ are on macOS where it’s the default, and the minimum macOS version we recommend uses llvm/clang/libc++ 8. You’d need to be using a years-old Linux distro to have GNU libstdc++ older than 7, or even libc++ older than 7 (e.g. Fedora 29 from 2018 has GNU libstdc++ 8 and libc++ 7).

The changed requirements for Lua will just stop people from using USE_SYSTEM_LIB_LUA with impunity. If you take the default of compiling Lua along with MAME, it will keep working.

I just think it’s important to let people know when requirements change.