(SOLVED) Error Updating ES From Source
-
@LiveFastCyYoung as others have also noted, the
internal compiler error
in your first post is caused by the low amount of RAM. Compiling can be memory intensive, so you might want to increase it as much as you can (change the GPU/RAM split, kill running programs).According to the setup script, uninstalling ES removes the binary and the config files. The RetroPie folder is not touched (unless there's an unknown side effect I'm not aware of).
You may build ES on your desktop PC, then transfer it to the Pi, but the process is considered as black magic and requires you to sacrifice your sanity on the altar of the Soul-Eating Compiler Demons.
-
@fluffypillow Thanks for the reply!
I have been able to free up to 700MB of RAM but it's still failing at 88%.
As far as the GPU/RAM split, what would you recommend other than the default?
-
@LiveFastCyYoung Just update from Binary.
-
@LiveFastCyYoung Allocate as much RAM as you can while you're building; if I remember correctly, you can set the GPU memory as low as 64 MB. 700 MB should be more than fine though, I wonder if there's something else in the logs...
Or you could also just update from binary.
-
@AlexMurphy The issue is that updating from Binary doesn't seem to be doing anything.
I am looking to use the new carousel theming feature and it's not working when updating from Binary. Maybe the binaries haven't been updated in awhile? I updated my Retropie Setup Script before every time I have tried updating from Binary.
Also, with this partially updated ES from source, certain things aren't working anymore. Most metadata is now blank being chief amongst them.
-
@LiveFastCyYoung The version of ES was bumped to 2.1.9 a few days ago. Try it.
-
All I know is that the most recent Source Update of Emulationstation seems to be breaking custom themes left and right. Metadata displaying improperly, video layers being messed up, subdolders not showing scraped art. Weird.
-
@KillerQ It's an issue with the z-index of images / text. AFAIK it is / should be sorted in the next Binary release or try from source, It's a known issue.
-
@KillerQ People are trying to make this better for everyone. No one has worked on ES for a long time. Things will go wrong and mess other stuff up. This is not "Apple" or "Google". People do this in their own time.
-
Took a bit more of fussing with it but, after 5 days I was finally able to get a full install from the binary.
Thanks for your help everyone! :)
-
Oh, it's all good. I love ES, and the recent progress is amazing. I don't mind bugs, I was just helping by sharing.
@AlexMurphy said in (SOLVED) Error Updating ES From Source:
@KillerQ People are trying to make this better for everyone. No one has worked on ES for a long time. Things will go wrong and mess other stuff up. This is not "Apple" or "Google". People do this in their own time.
-
@KillerQ I'm not criticising. I'm just reminding people. Any work on ES is good in the RP branch. Everyone benefits.
-
@LiveFastCyYoung I am still stuck at 89%. How did you manage to complete the installation?
-
@pjotresq I actually didn't. The binaries were finally updated and I went with those. Still can't update from source. ¯_(ツ)_/¯
-
Defintely appears to be related to limited memory.
I found this https://www.raspberrypi.org/forums/viewtopic.php?t=142243&p=940551#
sudo dd if=/dev/zero of=/swapfile1GB bs=1M count=1024
sudo mkswap /swapfile1GB
sudo swapon /swapfile1GBI tried all other recommendations noted here before doing this, but worked like a charm. I was getting stuck at 82% "SystemScreenSaver.cpp.oc++: internal compiler error".
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.