This package fails to build for me with the following error:
[ 95%] Building CXX object CMakeFiles/PPSSPPSDL.dir/UI/DevScreens.cpp.o
/home/robbie/ppsspp-git/src/ppsspp/UI/DevScreens.cpp: In member function ‘virtual void SystemInfoScreen::CreateViews()’:
/home/robbie/ppsspp-git/src/ppsspp/UI/DevScreens.cpp:149:2: error: ‘sort’ is not a member of ‘std’
std::sort(exts.begin(), exts.end());
^
/home/robbie/ppsspp-git/src/ppsspp/UI/DevScreens.cpp:157:2: error: ‘sort’ is not a member of ‘std’
std::sort(exts.begin(), exts.end());
^
make[2]: *** [CMakeFiles/PPSSPPSDL.dir/UI/DevScreens.cpp.o] Error 1
make[1]: *** [CMakeFiles/PPSSPPSDL.dir/all] Error 2
make: *** [all] Error 2
==> ERROR: A failure occurred in build().
Aborting...
Does anyone know what's wrong?
Search Criteria
Package Details: ppsspp-git 1.19.2.r189.1f2b4de6c1-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/ppsspp-git.git (read-only, click to copy) |
|---|---|
| Package Base: | ppsspp-git |
| Description: | A PSP emulator written in C++ |
| Upstream URL: | https://www.ppsspp.org/ |
| Licenses: | GPL-2.0-or-later |
| Conflicts: | ppsspp |
| Provides: | ppsspp |
| Submitter: | libcg |
| Maintainer: | loathingkernel |
| Last Packager: | loathingkernel |
| Votes: | 43 |
| Popularity: | 0.000540 |
| First Submitted: | 2012-11-05 20:36 (UTC) |
| Last Updated: | 2025-06-30 10:10 (UTC) |
Dependencies (28)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- gcc-libs (gcc-libs-gitAUR, gccrs-libs-gitAUR, gcc-libs-snapshotAUR)
- glew (glew-libepoxyAUR, glew-wayland-gitAUR, glew-gitAUR)
- glibc (glibc-gitAUR, glibc-eacAUR, glibc-git-native-pgoAUR)
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- libgl (libglvnd-gitAUR, amdgpu-pro-oglp-legacyAUR, nvidia-340xx-utilsAUR, amdgpu-pro-oglpAUR, nvidia-340xx-utils-macbookAUR, libglvnd)
- libpng (libpng-gitAUR, libpng-apngAUR)
- libzip (libzip-gitAUR)
- ppsspp-assets-gitAUR
- sdl2AUR (sdl2-gitAUR, sdl2-compat-gitAUR, sdl2-compat)
- sdl2_ttf
- snappy (snappy-gitAUR)
- zlib (zlib-gitAUR, zlib-ng-compat-gitAUR, zlib-ng-compat)
- zstd (zstd-gitAUR, zstd-staticAUR)
- clang (llvm-gitAUR, clang-minimal-gitAUR, clang17-binAUR) (make)
- cmake (cmake3AUR, cmake-gitAUR) (make)
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
- glew (glew-libepoxyAUR, glew-wayland-gitAUR, glew-gitAUR) (make)
- glu (glu-gitAUR) (make)
- libglvnd (libglvnd-gitAUR) (make)
- Show 8 more dependencies...
Required by (0)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 Next › Last »
robloy_ballobloy commented on 2013-10-03 12:33 (UTC)
someoneelse123 commented on 2013-09-15 16:18 (UTC)
/usr/share/ppsspp/assets/lang is not being installed.
Schala commented on 2013-07-31 09:29 (UTC)
Also, when you put in a pkgver() function, be sure to put epoch=1 in the PKGBUILD since Pacman will compare the git revision number to 20130726 and likely believe it to be an older version.
Schala commented on 2013-07-28 23:48 (UTC)
You need to put in a pkgver() function that will auto-set the pkgver. Here's one of mine for an example
pkgver() {
cd "$srcdir/${pkgname%-*}"
echo $(git rev-list --count master)
}
This will set the pkgver to the revision number for the repo.
libcg commented on 2013-07-28 11:08 (UTC)
Schala, I don't understand what you want.
Schala commented on 2013-07-28 01:52 (UTC)
Can you update this for Pacman 4.1? Thanks
libcg commented on 2013-07-26 20:47 (UTC)
Fixed LDFLAGS, fixed dependancies, removed PPSSPPHeadless.
kokoko3k commented on 2013-07-23 15:35 (UTC)
it fails for me on i686:
"Linking CXX executable PPSSPPSDL
/var/abs/local/yaourtbuild/ppsspp-git/src/ppsspp/ffmpeg/linux/x86_64/lib/libavformat.a: impossibile leggere i simboli: File format not recognized"
mvdan commented on 2013-07-12 13:25 (UTC)
I don't know how can some people compile from master without the extra LDFLAGS - perhaps there's something I'm missing? Flagging as out of date.
Pinned Comments
xdavidwu commented on 2021-02-09 03:30 (UTC)
Please don't flag this package out-of-date when you see the version string is. This is a VCS package. It always grabs the latest source from upstream repo and version string is generated at build time. As long as it builds fine, it is up-to-date. It is your responsibility to decide when to rebuild (update). I won't bump the version for you.
Also, I am running a daily build service, and by that, I can check that it builds fine daily. Ancient version string does not mean that I have loose track of the latest source.