Code Monkey home page Code Monkey logo

mupen64plus's People

Contributors

gizmo98 avatar grasevski avatar ricrpi avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mupen64plus's Issues

Raspberry Pi 2

I'm trying to build mupen64plus using build.sh as instructed, but I'm getting the same error as mentioned in issue #17.

../../src/api/vidext_sdl2_compat.h:34:2: error: #error SDL is not build with OpenGL ES2 support. Try USE_GLES=0

I tried to follow @NF3RN0's instructions on how to solve the problem, but I didn't get it to work.

Any news on getting the RaspbianList_Pi2 fully working, out of the box?

Thanks in advance!

I would really like to get this going on my Pi, instead of using Retropie, as I've read it's both faster and has the possibility to get high resolution texture packs (correct me if I'm wrong, or if this is possible through Retropie as well).

Makefile:107: Architecture "armv7l" not officially supported.'

Hi I have RPi 2 with raspberian. I dont want RetroPi.

I am trying to get mupen64plus working but I encounter the flowing output:

...
...
...
************************************ Building core library
make: Entering directory '/home/pi/mupen64plus-master/mupen64plus/ricrpi/mupen64plus-core/projects/unix'
Makefile:107: Architecture "armv7l" not officially supported.'
Makefile:296: *** No OpenGL development libraries found!. Stop.
make: Leaving directory '/home/pi/mupen64plus-master/mupen64plus/ricrpi/mupen64plus-core/projects/unix'

Can you help please?

Compilation Issues on RPi 3

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.

Compile on Raspberry Pi 3 fails

I've tried to compile mupen64plus twice with and without the raspbian list. Is there something I can do to fix this failed compile?

Error Output:

pi@raspberrypi:~/Documents/Compile/mupen64plus $ sudo ./build.sh RaspbianList_Pi2
SDL2 is missing the Raspberry PI Driver. You will not be able to run mupen64plus in the console.

--------------- Setup Information -------------
git version 2.1.4
             total       used       free     shared    buffers     cached
Mem:          590M       251M       339M        16M        12M       124M
-/+ buffers/cache:       114M       476M
Swap:         511M       3.6M       508M
gcc version 4.7.3 (Raspbian 4.7.3-11+rpi1) 
Build script: commit f06e16ff28e755a0bc4d5d846d7dcdcf7d8ddc4e
Jul  3 2017 14:16:43 
Copyright (c) 2012 Broadcom
version 4139c62f14cafdb7d918a3eaa0dbd68cf434e0d8 (tainted) (release)
DEV: 0
SDL2 2.0.3 located at /usr/local
gpu_mem=400
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
Raspbian GNU/Linux 8 \n \l

-----------------------------------------------
checking core from ricrpi is up-to-date
From https://github.com/ricrpi/mupen64plus-core
 * branch            ric_dev    -> FETCH_HEAD
Already up-to-date.
checking ui-console from mupen64plus is up-to-date
From https://github.com/mupen64plus/mupen64plus-ui-console
 * branch            master     -> FETCH_HEAD
Already up-to-date.
checking audio-omx from ricrpi is up-to-date
From https://github.com/ricrpi/mupen64plus-audio-omx
 * branch            master     -> FETCH_HEAD
Already up-to-date.
checking audio-sdl from mupen64plus is up-to-date
From https://github.com/mupen64plus/mupen64plus-audio-sdl
 * branch            master     -> FETCH_HEAD
Already up-to-date.
checking input-sdl from mupen64plus is up-to-date
From https://github.com/mupen64plus/mupen64plus-input-sdl
 * branch            master     -> FETCH_HEAD
Already up-to-date.
checking rsp-hle from ricrpi is up-to-date
From https://github.com/ricrpi/mupen64plus-rsp-hle
 * branch            master     -> FETCH_HEAD
Already up-to-date.
checking video-gles2rice from ricrpi is up-to-date
From https://github.com/ricrpi/mupen64plus-video-gles2rice
 * branch            master     -> FETCH_HEAD
Already up-to-date.
checking video-gles2n64 from ricrpi is up-to-date
From https://github.com/ricrpi/mupen64plus-video-gles2n64
 * branch            master     -> FETCH_HEAD
Already up-to-date.
checking rom from mupen64plus is up-to-date
From https://github.com/mupen64plus/mupen64plus-rom
 * branch            master     -> FETCH_HEAD
Already up-to-date.
************************************ Building core library
make: Entering directory '/home/pi/Documents/Compile/mupen64plus/ricrpi/mupen64plus-core/projects/unix'
Makefile:107: Architecture "armv7l" not officially supported.'
rm -f -r libmupen64plus.so.2.0.0 libmupen64plus.so.2 _obj
make: Leaving directory '/home/pi/Documents/Compile/mupen64plus/ricrpi/mupen64plus-core/projects/unix'
make: Entering directory '/home/pi/Documents/Compile/mupen64plus/ricrpi/mupen64plus-core/projects/unix'
Makefile:107: Architecture "armv7l" not officially supported.'
    CC  _obj/api/callbacks.o
    CC  _obj/api/common.o
    CC  _obj/api/config.o
    CC  _obj/api/debugger.o
    CC  _obj/api/frontend.o
    CC  _obj/api/vidext.o
    CC  _obj/main/main.o
    CC  _obj/main/util.o
    CC  _obj/main/cheat.o
    CC  _obj/main/eventloop.o
    CC  _obj/main/md5.o
    CC  _obj/main/rom.o
    CC  _obj/main/savestates.o
    CC  _obj/main/sdl_key_converter.o
    CC  _obj/main/workqueue.o
    CC  _obj/memory/dma.o
    CC  _obj/memory/flashram.o
    CC  _obj/memory/memory.o
    CC  _obj/memory/n64_cic_nus_6105.o
    CC  _obj/memory/pif.o
    CC  _obj/plugin/plugin.o
    CC  _obj/plugin/dummy_video.o
    CC  _obj/plugin/dummy_audio.o
    CC  _obj/plugin/dummy_input.o
    CC  _obj/plugin/dummy_rsp.o
    CC  _obj/r4300/r4300.o
../../src/r4300/r4300.c:233:13: warning: ‘dynarec_setup_code’ defined but not used [-Wunused-function]
    CC  _obj/r4300/cached_interp.o
    CC  _obj/r4300/cp0.o
    CC  _obj/r4300/cp1.o
    CC  _obj/r4300/exception.o
    CC  _obj/r4300/instr_counters.o
    CC  _obj/r4300/interupt.o
    CC  _obj/r4300/profile.o
    CC  _obj/r4300/pure_interp.o
    CC  _obj/r4300/recomp.o
    CC  _obj/r4300/reset.o
    CC  _obj/r4300/tlb.o
    CC  _obj/osal/dynamiclib_unix.o
    CC  _obj/osal/files_unix.o
    CC  _obj/r4300/empty_dynarec.o
    CC  _obj/r4300/new_dynarec/new_dynarec.o
In file included from ../../src/r4300/new_dynarec/new_dynarec.c:964:0:
../../src/r4300/new_dynarec/assem_arm.c: In function ‘isclean’:
../../src/r4300/new_dynarec/assem_arm.c:398:12: warning: pointer targets in initialization differ in signedness [-Wpointer-sign]
In file included from ../../src/r4300/new_dynarec/new_dynarec.c:964:0:
../../src/r4300/new_dynarec/assem_arm.c: In function ‘alloc_arm_reg’:
../../src/r4300/new_dynarec/assem_arm.c:911:3: warning: array subscript has type ‘char’ [-Wchar-subscripts]
../../src/r4300/new_dynarec/assem_arm.c: In function ‘do_cop1stub’:
../../src/r4300/new_dynarec/assem_arm.c:3000:7: warning: unused variable ‘rs’ [-Wunused-variable]
../../src/r4300/new_dynarec/assem_arm.c: In function ‘multdiv_assemble_arm’:
../../src/r4300/new_dynarec/assem_arm.c:4262:9: warning: "/*" within comment [-Wcomment]
../../src/r4300/new_dynarec/assem_arm.c:4226:21: warning: unused variable ‘lol’ [-Wunused-variable]
../../src/r4300/new_dynarec/assem_arm.c:4225:21: warning: unused variable ‘loh’ [-Wunused-variable]
../../src/r4300/new_dynarec/assem_arm.c:4224:21: warning: unused variable ‘hil’ [-Wunused-variable]
../../src/r4300/new_dynarec/assem_arm.c:4223:21: warning: unused variable ‘hih’ [-Wunused-variable]
../../src/r4300/new_dynarec/assem_arm.c: In function ‘wb_valid’:
../../src/r4300/new_dynarec/assem_arm.c:4433:14: warning: unused variable ‘new_hr’ [-Wunused-variable]
../../src/r4300/new_dynarec/new_dynarec.c: At top level:
../../src/r4300/new_dynarec/new_dynarec.c:938:17: warning: ‘ldl_merge’ defined but not used [-Wunused-function]
../../src/r4300/new_dynarec/new_dynarec.c:949:17: warning: ‘ldr_merge’ defined but not used [-Wunused-function]
In file included from ../../src/r4300/new_dynarec/new_dynarec.c:964:0:
../../src/r4300/new_dynarec/assem_arm.c:946:13: warning: ‘output_byte’ defined but not used [-Wunused-function]
../../src/r4300/new_dynarec/assem_arm.c:950:13: warning: ‘output_modrm’ defined but not used [-Wunused-function]
../../src/r4300/new_dynarec/assem_arm.c:1276:13: warning: ‘emit_addnop’ defined but not used [-Wunused-function]
../../src/r4300/new_dynarec/assem_arm.c:2477:13: warning: ‘emit_jno_unlikely’ defined but not used [-Wunused-function]
../../src/r4300/new_dynarec/new_dynarec.c: In function ‘address_generation’:
../../src/r4300/new_dynarec/new_dynarec.c:3889:9: warning: ‘ra’ may be used uninitialized in this function [-Wmaybe-uninitialized]
../../src/r4300/new_dynarec/new_dynarec.c: In function ‘storelr_assemble’:
../../src/r4300/new_dynarec/new_dynarec.c:3375:28: warning: ‘temp2’ may be used uninitialized in this function [-Wmaybe-uninitialized]
../../src/r4300/new_dynarec/new_dynarec.c:3213:7: warning: ‘memtarget’ may be used uninitialized in this function [-Wmaybe-uninitialized]
../../src/r4300/new_dynarec/new_dynarec.c: In function ‘store_assemble’:
../../src/r4300/new_dynarec/new_dynarec.c:3134:10: warning: ‘memtarget’ may be used uninitialized in this function [-Wmaybe-uninitialized]
../../src/r4300/new_dynarec/new_dynarec.c: In function ‘load_assemble’:
../../src/r4300/new_dynarec/new_dynarec.c:2958:10: warning: ‘memtarget’ may be used uninitialized in this function [-Wmaybe-uninitialized]
In file included from ../../src/r4300/new_dynarec/new_dynarec.c:964:0:
../../src/r4300/new_dynarec/assem_arm.c: In function ‘loadlr_assemble_arm’:
../../src/r4300/new_dynarec/assem_arm.c:3302:10: warning: ‘memtarget’ may be used uninitialized in this function [-Wmaybe-uninitialized]
../../src/r4300/new_dynarec/new_dynarec.c: In function ‘do_ccstub’:
../../src/r4300/new_dynarec/assem_arm.c:2027:33: warning: ‘addr’ may be used uninitialized in this function [-Wmaybe-uninitialized]
../../src/r4300/new_dynarec/new_dynarec.c:4734:11: note: ‘addr’ was declared here
../../src/r4300/new_dynarec/new_dynarec.c:4874:26: warning: ‘alt’ may be used uninitialized in this function [-Wmaybe-uninitialized]
../../src/r4300/new_dynarec/new_dynarec.c:4834:23: warning: ‘ntaddr’ may be used uninitialized in this function [-Wmaybe-uninitialized]
../../src/r4300/new_dynarec/new_dynarec.c: In function ‘new_recompile_block’:
../../src/r4300/new_dynarec/new_dynarec.c:9264:24: warning: array subscript is above array bounds [-Warray-bounds]
../../src/r4300/new_dynarec/new_dynarec.c:9264:43: warning: array subscript is above array bounds [-Warray-bounds]
../../src/r4300/new_dynarec/new_dynarec.c:6261:24: warning: ‘ntaddr’ may be used uninitialized in this function [-Wmaybe-uninitialized]
../../src/r4300/new_dynarec/new_dynarec.c:6116:16: note: ‘ntaddr’ was declared here
    CC  _obj/main/zip/ioapi.o
    CC  _obj/main/zip/zip.o
    CC  _obj/main/zip/unzip.o
    CXX _obj/osd/screenshot.o
    CC  _obj/memory/dma_arm.o
    CC  _obj/r4300/new_dynarec/linkage_arm.o
    LD  libmupen64plus.so.2.0.0
if [ "libmupen64plus.so.2" != "" ]; then ln -sf libmupen64plus.so.2.0.0 libmupen64plus.so.2; fi
make: Leaving directory '/home/pi/Documents/Compile/mupen64plus/ricrpi/mupen64plus-core/projects/unix'
************************************ Building ui-console front-end
make: Entering directory '/home/pi/Documents/Compile/mupen64plus/mupen64plus/mupen64plus-ui-console/projects/unix'
rm -f -r _obj mupen64plus
make: Leaving directory '/home/pi/Documents/Compile/mupen64plus/mupen64plus/mupen64plus-ui-console/projects/unix'
make: Entering directory '/home/pi/Documents/Compile/mupen64plus/mupen64plus/mupen64plus-ui-console/projects/unix'
    CC  _obj/cheat.o
In file included from ../../src/cheat.c:28:0:
../../src/core_interface.h:73:1: error: unknown type name ‘ptr_ConfigExternalOpen’
../../src/core_interface.h:74:1: error: unknown type name ‘ptr_ConfigExternalClose’
../../src/core_interface.h:75:1: error: unknown type name ‘ptr_ConfigExternalGetParameter’
Makefile:317: recipe for target '_obj/cheat.o' failed
make: *** [_obj/cheat.o] Error 1
make: Leaving directory '/home/pi/Documents/Compile/mupen64plus/mupen64plus/mupen64plus-ui-console/projects/unix'

Installing core library fails

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.

Raspberry Pi 2 build

Fresh build on a Raspberry pi 2.

SDL2 is missing the Raspberry PI Driver. You will not be able to run mupen64plus in the console.

I keep running into this and it won't continue the build. What can do? I have tried to run autoconf on SDL2 and build again but that did not help.

How to setup controls

Hi I was wondering how to setup controls for mupen64plus on my ras[#pberry pi 3 model b.
I have install mupen64plus and ran super mario 64 but i cannot control. I also have a USB controller.

Mario Kart 64 - Black Screens On Multiplayer

Hey,
thank you for this wonderful emulator!
But I have an issue with Mario Kart 64:
When playing Mario Kart 64 in multiplayer, only Player 1 is visible. All other players have a black screen.

Any suggestions?

Greetings

libmupen64plus.so.2.0.0 uses VFP register arguments, failed to merge target specific data

Hello!

First, thanks for this script, very usefull. I try to compile using ./dev_build.sh on my rpi and get this error:

    LD  libmupen64plus.so.2.0.0
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans0.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans0.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans1.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans1.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans2.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans2.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans3.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans3.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans4.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans4.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans5.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans5.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans6.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans6.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans7.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans7.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans8.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans8.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans9.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans9.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans10.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans10.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans11.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans11.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans12.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans12.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans13.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans13.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans14.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans14.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans15.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans15.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans16.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans16.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans17.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans17.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans18.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans18.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans19.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans19.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans20.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans20.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans21.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans21.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans22.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans22.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans23.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans23.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans24.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans24.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans25.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans25.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans26.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans26.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans27.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans27.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans28.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans28.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans29.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans29.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans30.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans30.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, /tmp/ccaP2mpO.ltrans31.ltrans.o does not
/usr/bin/ld: failed to merge target specific data of file /tmp/ccaP2mpO.ltrans31.ltrans.o
/usr/bin/ld: error: libmupen64plus.so.2.0.0 uses VFP register arguments, _obj/r4300/new_dynarec/linkage_arm.o does not
/usr/bin/ld: failed to merge target specific data of file _obj/r4300/new_dynarec/linkage_arm.o
collect2: error: ld returned 1 exit status
Makefile:604: recipe for target 'libmupen64plus.so.2.0.0' failed
make: *** [libmupen64plus.so.2.0.0] Error 1
make: Leaving directory '/home/pi/code/mupen64plus/ricrpi/mupen64plus-core/projects/unix'

It seems to be related to hardfloat softfloat.

I'm using raspbian. My gcc-4.7 is:

$ gcc-4.7 -v
Using built-in specs.
COLLECT_GCC=gcc-4.7
COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.7/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.2-5+rpi1' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.7 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libitm --enable-plugin --enable-objc-gc --disable-sjlj-exceptions --with-arch=armv6 --with-fpu=vfp --with-float=hard --enable-checking=release --build=arm-linux-gnueabihf --host=arm-linux-gnueabihf --target=arm-linux-gnueabihf
Thread model: posix
gcc version 4.7.2 (Debian 4.7.2-5+rpi1) 

Any idea?

Thanks in advance! :)

build.sh bugs with SDL2 detection

In build.sh line 171 you have if checking for /usr/local/lib/libSDL2.so

if it finds it (true in my case as I have SDL2 locally installed), the script will then fail with the next pushd which does

"pushd ${BUILDDIR}/${SDL2}" which gets run even if SDL hasn't been downloaded.

install mupen64plus in raspian raspberry pi 3 issues

first i get this problem

In file included from ../../src/api/vidext.c:38:0:
../../src/api/vidext_sdl2_compat.h:34:2: error: #error SDL is not build with OpenGL ES2 support. Try USE_GLES=0
Makefile:630: recipe for target '_obj/api/vidext.o' failed
make: *** [_obj/api/vidext.o] Error 1
make: Leaving directory '/home/pi/mupen64plus/ricrpi/mupen64plus-core/projects/unix'


after this i removed my sdl2 and i build again
and new problem

make: Entering directory '/home/pi/mupen64plus/ricrpi/mupen64plus-core/projects/unix'
Makefile:107: Architecture "armv7l" not officially supported.'
Makefile:296: *** No OpenGL development libraries found!. Stop.
make: Leaving directory '/home/pi/mupen64plus/ricrpi/mupen64plus-core/projects/unix'
help please ?

mupenplus-core ric_dev Makefile error

Hi,

Only a minor bug, but on line 101 of the projects/unix/Makefile in the ric_dev branch of your mupenplus64-core repository the "else if" statement is not correct, it should read "else ifeq".

Cheers,

Neil.

Help running roms

I may be a total noob here, but I can't figure out how to run a rom. Can anyone help me? Thanks.

g++-4.7 package does not exist

When I try too run build.sh it throws the following error:

You should install the GCC 4.7 compiler
Either run this script with sudo/root or run 'apt-get install gcc-4.7'

If I run it with sudo I get the following error:

Note, selecting 'gcc-4.7-doc' for regex 'gcc-4.7'
Note, selecting 'gcc-4.7-base' for regex 'gcc-4.7'
gcc-4.7-doc is already the newest version (4.7.4-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
************************************ Downloading/Installing G++ 4.7
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package g++-4.7
E: Couldn't find any package by glob 'g++-4.7'
E: Couldn't find any package by regex 'g++-4.7'

So I assume that the package doesn't exist anymore.

I hope this is still maintained...

'Legend of Zelda - The, Ocarina of time' extremely laggy

'Legend of Zelda - The, Ocarina of time' (and majora's mask) are extremely laggy. just as Mario Kart 64 was in the beginning.

Sidenote:
Dear developers, i am following this project for a while now (for my retropie) and i was wandering, is the mugel64plus for retropie (i guess this version) a different version than the one on windows ?

Trying to install...

Hello!

I am kind of a noob at this, and also at Linux, but when I'm trying to install mupen64plus with this package, it doesn't work, or maybe it's me that doesn't work ( :S ).
Anyway, I completed the build.sh script, and proceed to execute the install.sh script, It looks like this: http://i.imgur.com/SunKahV.png
Important to note, in that case, I tried with the "Install" but it neither works with that or "Install.sh".
Help is greatly appreciated!

Some issues in Raspbian (RPi 3)

Hello, I am having some issues with the latest compiled version of this emulator and I hope to fix at least a couple of them with your kind support:

1st: Configuration folder not being saved
I have to explicitly put the option --configdir /home/pi/.config/mupen6plus every time, or the emulator would load different configurations. Where are such configurations to be found?

2nd: Core event commands not working
Pressing esc to quit the emulator, as well as all of the other commands do not work, though they are correctly bound inside of mupen64plus.cfg. Could these by disabled by default in compilation time? How do I check this?

3rd: Unchangeable fullscreen resolution
The fullscreen resolution is automatically taken to be the one that Raspbian is running in. This is a problem because such resolution is too high for most games to run smoothly. I can change the default resolution to be lower, but I'd much rather keep it native and change it only within mupen64plus. Is it possible?

Thanks for your time and work.

Build Issue - OpenGL ES2 Support

I have had some issue with getting the Build file to run to install Mupen64 on my Raspberry Pi 4. I have managed to resolve a couple issues, but am currently getting this error:

Makefile:107: Architecture "armv7l" not officially supported.'
CC _obj/api/vidext.o
In file included from ../../src/api/vidext.c:38:
../../src/api/vidext_sdl2_compat.h:34:2: error: #error SDL is not build with OpenGL ES2 support. Try USE_GLES=0
#error SDL is not build with OpenGL ES2 support. Try USE_GLES=0
^~~~~
make: *** [Makefile:630: _obj/api/vidext.o] Error 1
make: Leaving directory '/home/pi/mupen64plus/ricrpi/mupen64plus-core/projects/unix'

Can someone help with getting this issue resolved?
Any help would be appreciated.

Keyboard and fullscreen not working.

Took me a little bit to get it compiled and start testing again. Fresh NOOBS Install from the non-dev branch. I did have to set APIDIR manually from the console when I compiled. Keyboard is not working, and it worked in previous builds, I have tried everything. The other thing I cannot get to work is the screen sized is windowed on the bottom left corner, tried everything I knew to force it to fullscreen. Everything else seems to work just fine or better than it did before.

Problem when parsing defaultList

Hello

I have a following problem

When I run the build.sh script it finishes with following error:

error: The requested URL returned error: 403 while accessing https://github.com/VFP=1/mupen64plus-VFP=1/info/refs fatal: HTTP request failed

This is probably a problem with parsing of the defaultList file because VFP=1 is used as a flag for the mupen64plus-core component. For some reason the script is treating it as a separate component, which of course does not exist.

Thank you for your help

build.sh cant find mupen64 api headers

When running build.sh I get to this error after about 20 minutes:

        ...(output omitted)...
    LD  libmupen64plus.so.2.0.0
if [ "libmupen64plus.so.2" != "" ]; then ln -sf libmupen64plus.so.2.0.0 libmupen64plus.so.2; fi
make: Leaving directory `/home/pi/mupen64plus/ricrpi/mupen64plus-core/projects/unix'
************************************ Building ui-console front-end
make: Entering directory `/home/pi/mupen64plus/mupen64plus/mupen64plus-ui-console/projects/unix'
Makefile:159: *** Mupen64Plus API header files not found! Use makefile parameter APIDIR to force a location..  Stop.
make: Leaving directory `/home/pi/mupen64plus/mupen64plus/mupen64plus-ui-console/projects/unix'

I think the source is not being downloaded into the correct folders. In the mupen64plus-rpi repository, each component sits in the same folder, called 'source'. After attempting to run build.sh, I have two folders:

ricrpi/
  |-- mupen64plus-audio-omx/
  |-- mupen64plus-core/
  |-- mupen64plus-rsp-hle/
  |-- mupen64plus-video-gles2n64/
  |-- mupen64plus-video-gles2rice/

and

mupen64plus/
  |-- mupen54plus-audio-sdl
  |-- mupen54plus-input-sdl
  |-- mupen54plus-rom
  |-- mupen54plus-ui-console

The error suggests that the build is currently in the folder /home/pi/mupen64plus/mupen64plus/mupen64plus-ui-console/projects/unix. According to the make file, at this point, it will look for the api header files in a relative location of ../../../mupen64plus-core/src/api. However, given how the files were laid out for me, it will look for mupen64plus-core in /home/pi/mupen64plus/mupen64plus/, but it is not there. It is in /home/pi/mupen64plus/ricrpi/.

This seems like a bug, probably caused by using a relative path somewhere.

No audio in Raspberry Pi 3 build?

Hello everyone. I have followed the instructions for the compilation of mupen64plus on my new Raspberry Pi 3. I have encountered several issues before being able to compile, some of which seem to have gone away. I had to reinstall SDL2 because Raspbian does not have it in the expected location, I also had to install some OpenGL development libraries. The emulator still would not compile because of a neon related issue, which I still am having issues with. I managed to obtain a "working" binary by removing the OPTFLAGS=-flto -mfpu=neon line from RaspbianList_Pi2 and subsequently using it. I also had to specify the API directory in order for it to compile, though it appears SDL is not able to initialize my audio subsystem because "no such system found" appears.

I am new at this so I apologize if I'm wasting anybody's time with my dullness, but how can I check my configurations? I ran these commands in order to install SDL2 properly

wget https://www.libsdl.org/release/SDL2-2.0.3.tar.gz
tar zxvf SDL2-2.0.3.tar.gz
cd SDL2-2.0.3 && mkdir build && cd build
../configure --host=armv7l-raspberry-linux-gnueabihf --disable-pulseaudio --disable-esd --disable-video-mir --disable-video-wayland --disable-video-x11 --disable-video-opengl
make -j 4
sudo make install

I have not removed the prepackaged installation of SDL2. Thanks.

installation on a rpi2? openGL error on build!

I am trying to install the mupen64plus on the new Raspberry Pi 2 and I am having some major setbacks....and although I have read and tried the tips mentioned on issues/17 by NF3RNO I cannot the build to successfully complete. The installation is being performed on fresh image of raspbian after the basic update and upgrade commands.....Following the readme the commands: git clone https://github.com/ricrpi/mupen64plus and cd mupen64plus run successfully. But the command ./build.sh RaspbianList_Pi2 which I run w/ sudo builds halfway (i think) only to output an error stating I am missing openGL. I am not sure why considering openGL is supposed to be installed.

Then I tried to reconfigure the SDL2-2.0.3 using sudo ./configure --disable-video-opengl --disable-video-x11 --host=armv7l-raspberry-linux-gnueabihf --enable-video CPPFLAGS=-I/opt/vc/include
then sudo make; and sudo make install. But after configuration on sudo make I receive a new error Makefile:159: **Mupen64plus API header files not found!

./build.sh does not work

When I do the command ./build.sh, the terminal displays a message saying: installer updated, re-run build.sh

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.