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

Compilation Issues on RPi 3 #28

Open
AlessandroPorcelli91 opened this issue Sep 3, 2016 · 2 comments
Open

Compilation Issues on RPi 3 #28

AlessandroPorcelli91 opened this issue Sep 3, 2016 · 2 comments

Comments

@AlessandroPorcelli91
Copy link

AlessandroPorcelli91 commented Sep 3, 2016

Hello there, I can see in the latest version of RaspbianList_2 it is reported that the core library should now be compiled from the official repo of mupen64plus. However, I am encountering an issue using build.sh with that option.

/usr/include/arm-linux-gnueabihf/gnu/stubs.h:7:29: fatal error: gnu/stubs-soft.h: No such file or directory
compilation terminated.
Makefile:665: recipe for target '_obj/ai/ai_controller.o' failed
make: *** [_obj/ai/ai_controller.o] Error 1
make: Leaving directory '/home/pi/mupen64plus/mupen64plus/mupen64plus-core/projects/unix'


It may very well work, it sounds more like a silly compiler issue than else to my noob ears. What's going on? Another issue I find is that unless I comment out "-mfpu=neon" from gles2n64 in RaspbianList_2 I get

make: Leaving directory '/home/pi/mupen64plus/ricrpi/mupen64plus-video-gles2n64/projects/unix'
make: Entering directory '/home/pi/mupen64plus/ricrpi/mupen64plus-video-gles2n64/projects/unix'
make: pu=neon: No such file or directory
make: *** No rule to make target 'pu=neon'.  Stop.
@AlessandroPorcelli91 AlessandroPorcelli91 changed the title Compiling the core from the official repo is not working Compilation Issues on RPi 3 Sep 3, 2016
@gizmo98
Copy link
Collaborator

gizmo98 commented Sep 4, 2016

@AlessandroPorcelli91
Copy link
Author

@gizmo98 Thanks for responding. It appears that I have it already installed and updated to the latest version, so that's probably something else causing this. Thanks though.

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