-
Notifications
You must be signed in to change notification settings - Fork 13
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
ppsspp-libretro-1.0_pre20180317-r1 build failure #107
Comments
ppsspp-libretro seems to have been rebased a few days ago. That means that the src users downloaded before that time are incompatible with current upstream. Please delete I bumped the ebuild just in case there are still missing refs at the old commit. |
Now it fetches, but compilation fails with
|
Yeah, a fix is already commited to original upstream but didn't land on libretro yet. I hope I chose a commit that works for now. |
New ebuild didn't change a thing. I deleted |
This one includes the fix I was talking about. |
|
Perhaps, you need to package v1.5.4 from https://github.com/libretro/ppsspp/releases |
I took a peek into the Makefile and noticed that the sed lines aren't needed anymore and had the potential to break building. I think that was responsible for this. The releases are from upstream ppsspp and don't include libretro. |
|
In the past I caught these things almost as soon as they happened because I used to sync everyday and used smart-live-rebuild to be up-to-date upstream. But it's true that it is bothersome that upstream changes their underwear so often. The most reliable way is to host the non-9999 sources somewhere save and fetch them from there. Perhaps we could use github in some way to deliver them, I think I can upload binary files when making a tag release and edit it according to version bumps. Well, that will have to wait until I have gentoo again so that I can get all needed tarballs to calculate if github would be able to host them. |
Hello,
trying to build this package gives me
I have no idea of what it means.
The text was updated successfully, but these errors were encountered: