@buzz All good! With the official script I can compile fine what I needed!

@Raleighguy The concurrency is set automatically, based on the #of CPUs you have and the system you're running on. On a PI3, it's probably 2, since it doesn't have enough memory and CPU anyway to sustain 4 compilation threads.

Of course, that worked like a charm. Thank you for the support!

@shadowron If the OOM kicked in and the system crashed, then I'd say it's normal the log is corrupted.

Actually, your mileage may vary by doing this when it comes to the emulators because although they all compiled, some of them crashed when executed. Much better to use the latest 16.04 LTS or later on a PC with a CPU with core2duo or later.

@mitu Oh I'm aware it's just a front end, I've tried doing RetroPie for my brother in law as a Christmas gift (which I got working easily enough). And I didn't think to try Github's instructions, I guess I just assumed the main page would work. Tired and ready for bed. Thanks, I'll give it a shot later.

I looked for 3 days for an answer... apparently not hard enough. Thank you very much!

@mitu said in Advance MAME won't make a working compile on Ubuntu 17.10: CFLAGS="-fno-stack-protector" I created a pull request in github.

@dudleydes Hi there. I know this thread is quite old, bit wonder if you can help me please. I already have Scummvm (SDL1) installed in Retropie and the games run - albeit with the less-than-ideal controller configuration. Could I just follow your instructions (replacing scummvm with scummvm-sdl1) up to the point of editing and saving sdl-events.ccp? I tried running through the full thing and it broke my install of Scummvm (thank the lord for backup images!), and so I'm not sure what else to try. I should say I have no understanding of coding whatsoever, I'm just trying to work my way through this by following the explicit instructions of helpful folk like yourself. Many thanks for any pointers you can give me. Mark

@aryetis that's the joy of open source projects. Many projects we use come from upstream so when things break it's often nothing we've done and issues and fixes need to be done upstream. Just for reference this is the repo for desmume and you can see in the recent commit history some changes were made to the makefile and those may have broken the compilation: https://github.com/libretro/desmume

@lordg2009 same results here. a menu opened up very momentarily but then things crashed so... yeah idk. maybe it needs x and doesnt like running on the framebuffer. have you tried bombic? https://sourceforge.net/projects/bombic/

@BuZz that make sense, I forgot that RetroPie is not exclusive for Raspbian.

@BuZz I already own a Rpi3 but as C1 is more powerfull i wanted to give it a try. I Already tried Lakka once but it misses the emulationstation front end and there lot of tool missing compared to RetroPie I only wished there was an already build image for C1 like the one for RPI but it appears to be in my dreams. So i'll stop posting here and open a new thread with the proper information. Thanks for helping me it been beyond my expectation so far :)

There are issues with it still imho - in the GUI, the mouse position is incorrect vs where the pointer is (makes it somewhat tricky to configure). The default opengl mode doesn't seem to work either - at least on grim fandango (software rendering seems ok though).

@BuZz No overclocked, dmesg say "Out of memory: Kill process 27546 (cc1plus) score 413 or sacrifice child". The complete dmesg: http://pastebin.com/jTHKLBQr. I'm trying with lightdm disabled. Thanks. Edit: Fail without lightdm, I will try with multiboot.

https://github.com/RetroPie/RetroPie-Setup/pull/1773

@BuZz all right, bought a new one, waiting for it to arrive. but the "flash" signal shouldn't be appearing then?

thx for the help, finally got it compiled, but it mostly just crashes back to retroarch 10 seconds into startup on the games I wanted it for. ahh, well, that's why it's called experimental.

Ok Guys... today building went fine \o/ I trust the root cause was overheating. In fact we suffered from an impressive heatwave over there and like me my pi didn't enjoy it!!! I do confirm: I've changed nothing compare to yesterday (despite my low disk space, power plug and "lower" overclock settings :p) I feel better now first because the air temperature is way more acceptable for a human being (and for the pi). Second because my setup is not at fault and I know that I got an up to date and proper raspbian version. All good news. Thanks a lot for the support and sorry for that post, useless in fact :(