Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Error building PPSSPP 0.9.7 on OSX
#1
Hello,
I'm trying to build PPSSPPSDL 0.9.7 on OSX 10.7.5, but cmake fails giving me those errors:

Generating something_that_never_exists
-- Found Git: /usr/bin/git (found version "1.7.12.4 (Apple Git-37)")
CMake Warning at git-version.cmake:40 (message):
UPDATE: /Applications/Emulators/PPSSPP/SourceCode/ppsspp/git-version.cpp

Undefined symbols for architecture x86_64:
"___sincos_stret", referenced from:
_ff_mdct_init in libavcodec.a(mdct_float.o)
_ff_ps_init in libavcodec.a(aacps.o)
"___sincosf_stret", referenced from:
_ff_ps_init in libavcodec.a(aacps.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [PPSSPPSDL] Error 1
make[1]: *** [CMakeFiles/PPSSPPSDL.dir/all] Error 2
make: *** [all] Error 2

Can someone help me solve this problem?
Thanks in advance for your help.
Reply
#2
Seems like an ffmpeg problem. You'll probably need to rebuild ffmpeg:

cd ffmpeg
./mac_x86-64.sh
cd ../build
make

http://stackoverflow.com/questions/19015...en-linking

I think the ffmpeg mac libs are built for a newer Mac OS X version.

-[Unknown]
Reply
#3
I ran the commands you posted (I had to install yasm first) but there still are errors, even if different.

Generating something_that_never_exists
-- Found Git: /usr/bin/git (found version "1.7.12.4 (Apple Git-37)")
CMake Warning at git-version.cmake:40 (message):
UPDATE: /Applications/Emulatori/PPSSPP/SourceCode/ppsspp/git-version.cpp

Linking CXX executable PPSSPPSDL
Undefined symbols for architecture x86_64:
"_ff_xvmc_init_block", referenced from:
_mpeg_decode_slice in libavcodec.a(mpeg12dec.o)
"_ff_xvmc_pack_pblocks", referenced from:
_mpeg_decode_slice in libavcodec.a(mpeg12dec.o)
"_iconv", referenced from:
_avcodec_decode_subtitle2 in libavcodec.a(utils.o)
"_iconv_close", referenced from:
_avcodec_open2 in libavcodec.a(utils.o)
_avcodec_decode_subtitle2 in libavcodec.a(utils.o)
"_iconv_open", referenced from:
_avcodec_open2 in libavcodec.a(utils.o)
_avcodec_decode_subtitle2 in libavcodec.a(utils.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [PPSSPPSDL] Error 1
make[1]: *** [CMakeFiles/PPSSPPSDL.dir/all] Error 2
make: *** [all] Error 2
Reply
#4
That's interesting. Try removing mjpeg:

https://github.com/hrydgard/ppsspp-ffmpe...nt-5177869

-[Unknown]
Reply
#5
(02-14-2014, 09:01 PM)[Unknown] Wrote: That's interesting. Try removing mjpeg:

https://github.com/hrydgard/ppsspp-ffmpe...nt-5177869

-[Unknown]

I removed --enable-encoder=mjpeg from mac_x86-64.sh and repeated the commands you posted, but I still received the same errors. Do I need to remove the reference to mjpeg in other files?
Reply
#6
Hmm, no that would be the only place. I'm not sure why the build you got of ffmpeg is missing symbols...

-[Unknown]
Reply
#7
(02-15-2014, 01:42 AM)[Unknown] Wrote: Hmm, no that would be the only place. I'm not sure why the build you got of ffmpeg is missing symbols...

-[Unknown]

The build of ffmpeg that I downloaded in December in the 0.9.6 repository had no problem and linked correctly during the build process. If I revert to that version there's the risk to break some functionality in PPSSPP?

Or, isn't it possible that whoever rebuilt MACOSX ffmpeg with OSX 10.9 two months ago can do the build again adding the necessary flags to make the build retrocompatible? The original problem was just in two symbols, ___sincos_stret and ___sincosf_stret, that were introduced in OSX 10.9 (and right now OSX 10.9 has lots of problems, so it's quite common to not upgrade to it and remain to OSX 10.7/10.8).
Reply
#8
Possibly. The older version of ffmpeg from 0.9.6 just crashes a bit more, you won't be missing that much.

-[Unknown]
Reply
#9
I did a git checkout 2e462e2c1a606d1c8c80ea6e72d38a1f3be91488 inside the ffmpeg submodule and with those libraries building PPSSPPSDL was successful. I will test if the emulator works correctly in the following days.
Reply


Forum Jump: