Previous Thread
Next Thread
Print Thread
Page 2 of 2 1 2
Joined: Mar 2009
Posts: 57
M
Member
Offline
Member
M
Joined: Mar 2009
Posts: 57
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: 709
Likes: 13
G
Senior Member
Offline
Senior Member
G
Joined: Feb 2014
Posts: 709
Likes: 13
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.

Page 2 of 2 1 2

Moderated by  R. Belmont 

Link Copied to Clipboard
Who's Online Now
2 members (gspat, shattered), 27 guests, and 2 robots.
Key: Admin, Global Mod, Mod
ShoutChat
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Forum Statistics
Forums9
Topics9,018
Posts118,409
Members5,010
Most Online890
Jan 17th, 2020
Forum Host
These forums are hosted by www.retrogamesformac.com
Forum hosted by www.retrogamesformac.com