Previous Thread
Next Thread
Print Thread
Page 2 of 2 1 2
Joined: Mar 2009
Posts: 75
Likes: 2
M
Member
Offline
Member
M
Joined: Mar 2009
Posts: 75
Likes: 2
Quote
I could be wrong but I see -Werror which can usually be counteracted by adding NOWERROR=1 in your make string. Give that a try.


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.

Code
$ export QT_SELECT=qt5
$ make -j9 CFLAGS='-U_FORTIFY_SOURCE' NOWERROR=1

Thanks.

Joined: Feb 2014
Posts: 1,034
Likes: 119
G
Very Senior Member
Offline
Very Senior Member
G
Joined: Feb 2014
Posts: 1,034
Likes: 119
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.

Joined: Jan 2009
Posts: 68
P
Procyon Offline OP
Member
OP Offline
Member
P
Joined: Jan 2009
Posts: 68
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.

Last edited by Procyon; 03/31/23 03:29 AM.
Joined: Feb 2004
Posts: 2,561
Likes: 263
Very Senior Member
Offline
Very Senior Member
Joined: Feb 2004
Posts: 2,561
Likes: 263
Originally Posted by Procyon
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.

Page 2 of 2 1 2

Moderated by  R. Belmont 

Link Copied to Clipboard
Who's Online Now
2 members (R. Belmont, 1 invisible), 63 guests, and 1 robot.
Key: Admin, Global Mod, Mod
ShoutChat
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Forum Statistics
Forums9
Topics9,293
Posts121,521
Members5,067
Most Online1,283
Dec 21st, 2022
Our Sponsor
These forums are sponsored by Superior Solitaire, an ad-free card game collection for macOS and iOS. Download it today!

Superior Solitaire
Forum hosted by www.retrogamesformac.com