Closed cpg closed 9 years ago
first / second error can be ignored
Will check snesdev, was this from selecting it from the setup menu ?
libretrocore mupen64plus will need rebuilding from source to rectify that error (until a new binaries package is available - it was an issue that has been fixed but will require a new distribution of the binaries)
This was doing the whole binary install.
probably related to changes that have happened since the binaries were last packaged. you can re-run the snes dev stuff manually from the setup menu, or by doing
sudo ./retropie_packages.sh snesdev
if you don't use snes controllers you can just ignore it though.
(Will leave this ticket open until we have a new binary package and I'll run through and test it - we have had some changes in recent weeks that may have introduced a few glitches here and there). Thanks for the feedback.
Running sudo ./retropie_packages.sh snesdev
seems to have worked, though it brings me to an option to run it on boot, which, I think?, would conflict with ES?
In any case that part worked. I was also able to run the GBA emulator, so the install was not completely broken after all. Good going.
Incidentally, I am not sure if this weird root prompt is added by the rp-setup script or RP or raspbian, but it's weird, because I (as a new user) do not know what a "system" is per se, though I think it's talking about an emulator, based on the next sentence. Also, I do have some games on at least the GBA emulator.
No, I do not know what es_systemc.cfg is, what is the "for XML" context or why the system is somehow waiting for ... I have to type ctrl-c to get going ...
pi@raspberrypi ~/RetroPie-Setup $ sudo su -
lvl0: No systems found! Does at least one system have a game present? (check that extensions match!)
(Also, make sure you've updated your es_systems.cfg for XML!)
^Croot@raspberrypi:~#
If this is part of the rp-setup script, it would probably make sense to not do this or explain why it's trying this ... However, since most users will never need to do things as root, hopefully, this is not a major issue.
It's due to the way emulationstation is configured to run on startup.
You can just "sudo -s" for a non login shell to run stuff as root.
Great job on the installer, guys!
I got some errors, so I thought I would report them as a Clueless End User, in the hopes that this is useful to the team.
Considering the amount of bits that have to lined up here, this is a remarkable feat!
My setup is RetroPieImage_ver2.3.img with the RetroPie-Setup as of master/c782fdc706e74. The mention that the install is likely broken is a bit unsettling, even if it provides a work-around.
First error:
The second error is:
The third error is:
Fourth error: