Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installing core library fails #14

Open
scottCheezem opened this issue Feb 10, 2015 · 3 comments
Open

Installing core library fails #14

scottCheezem opened this issue Feb 10, 2015 · 3 comments

Comments

@scottCheezem
Copy link

from default rasbian install with user name pi, I can clone the repo to my home directory with gcc installed.
I then run sudo ./build.sh which gives every indication of completing successfully.
then I run
sudo ./install.sh

************************************ Installing core library
make: *** /home/pi/mupen64plus/ricrpi/mupen64plus-core/projects/unix: No such file or directory. Stop.

@parkersikand
Copy link

I had this same problem. What happens when you run ./build.sh again?

On my system, If I ran build.sh again, it spit out the "Setup Information", up until the location of SDL. By throwing some "echos" into the script, I verified that the script was dying around line 335, where the script is looking for the "gpu_mem" directive in the /boot/config.txt file. I did not have this in my config file. Once I added "gpu_mem=64", as suggested here, the script is able to move on, and actually download and (attempt to) build the actual mupen64-core.

So perhaps better error reporting is needed... I can hack something up quickly and make a pull request.

@parkersikand
Copy link

It's probably bad form to monkey with a user's /boot/config.txt file, but if the directive is not present, can "gpu_mem=64" be safely added, since it is the default? Or perhaps the script should try to discover the GPU mem a different way?

@scottCheezem
Copy link
Author

I tried adding the gpu_mem=64 to my /boot/config.txt
that seems to get the build going and after I can run the install.sh with root priv without errors (that I noticed). I may have messed something up along the way though as now when I try to run the emulator I get
Core Warning: No video plugin attached. There will be no video output.
still investigating, but thanks for the tip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants