Building packages with retropie_packages.sh has terrible results!

ProxyCell

I decided to just run a long script to build a bunch of packages on a fresh Jessie raspbian setup. I have done these a thousand times but I normally just use the retropie_setup.sh interface

My script looked roughly like this:
sudo ./retropie_packages.sh pifba
sudo ./retropie_packages.sh mame4all
etc, etc, etc

Not only did most of these fail to create their respective ROM directories (~/RetroPie/roms/nes/) but even after I have created them manually, EmulationStation refuses to load and instead throws up an error:
terminate called after throwing an instance of 'boost::filesystem::filesystem_error'
what(): boost::filesystem::status: Permission denied: "/root/RetroPie/roms/atari7800"
Aborted

Notice that "atari7800"? - Well, thats because I went into the retropie_setup.sh script and build mame4all (so arcade is good now!) and then I rebooted, had to do atari2600 and now its on to atari7800 - it appears I will have to rebuild at least one emulator for every single directory :(

What have I done wrong here? I'm guessing the fault lies with something I did as I'm sure other people are using the retropie_packages.sh script successfully!

Additional: I did try running the "reset roms directory" option in the setup script as well.

mitu

@proxycell Most people are using retropie_packages.sh through the setup script and this is why they don't have problems. It seems the ES installation has generated the wrong es_systems.cfg, pointing to the /root home instead of the pi user homedir and that's why you get the ES errors and the missing ROM folders.

Is there a reason you don't use the setup script directly and install from binaries, instead compiling them ?

As to why the packages script does not produce the intended results, are you running the script as root instead of the pi user ?

ProxyCell

@mitu
thanks for the reply!

I figured running them as root was the smart idea as the setup script is run as such too... so this is the result of me trying to be "smart" here, eh? LOL
so if I run them as "pi" it would have been fine?

I decided to run them from the retropie_packages script this time as I like to build out a lot of the arcade emulators from source

FYI - I'm now past FBA and onto FDS lol...

mitu

@proxycell said in Building packages with retropie_packages.sh has terrible results!:

I decided to run them from the retropie_packages script this time as I like to build out a lot of the arcade emulators from source

Why do you think you need to build from source ? Is there a reason to prefer this over the pre-built binaries ?

ProxyCell

just automation? unless there is a way for me to pull binaries in a similar manner...

ProxyCell

let me add to this in another post:
I make one change to the building of ES (it works, tested previously many times) and so I figured, why not just automate the building of everything so I don't need to pull everything manually?

mitu

@proxycell If you already have RetroPie set up, the setup script has the option do update all packages, which does exactly this - updates from binary each package, with just one operation.
I think the initial install does the same - installs the binaries for the core packages.

ProxyCell

@mitu ahh, see, I'm not building off of a RetroPie image - doing it from a Jessie Lite one - where nothing is pre-installed

mitu

@proxycell The RetroPie image available to download is based on Raspbian Jessie Lite. If you're starting from scratch, I think it's easier to just get the RetroPie image and flash it on the sd card.

ProxyCell

while I agree it is easier, it comes with some packages I'd rather avoid and I just rebuilt everything (from binary this time!) just the way I like it ;)

herb_fargus

@proxycell said in Building packages with retropie_packages.sh has terrible results!:

it comes with some packages I'd rather avoid

Which can easily be uninstalled through the setup script too.