mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-26 08:15:59 +03:00
[GH-ISSUE #1994] [APP BUG]: Build broken on gcc due to issues in some of the amdgpu files #688
Labels
No labels
Bloodborne
bug
contributor wanted
documentation
enhancement
frontend
good first issue
help wanted
linux
pull-request
question
release
verification progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shadPS4#688
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @C0rn3j on GitHub (Dec 31, 2024).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/1994
Checklist
Describe the Bug
I am guessing this was introduced by #1869
Reproduction Steps
Attempt to build AUR/shadps4-git -> this error
Judging by the Ubuntu CI passing on this, I am guessing something here on Arch is more strict. Seems to be clang vs gccI could not spot anything off about the recent changes vs the PKGBUILD other than having an extra cubeb dependency, which should be completely irrelevant to this issue.
Expected Behavior
No response
Specify OS Version
Arch Linux
@rharish101 commented on GitHub (Dec 31, 2024):
I modified the PKGBUILD to build shadPS4 with Clang instead of GCC, and it builds (and runs well). Here is the diff for the PKGBUILD:
Therefore, I think the title should be renamed to reference that it is a GCC vs Clang problem.
@tomboylover93 commented on GitHub (Jan 1, 2025):
@abouvier You maintain the shadps4-git PKGBUILD, so you should look into replacing the default compiler with Clang as outlined above. It would be good practice as well as it is recommended over GCC.
@C0rn3j commented on GitHub (Jan 1, 2025):
I think an actual solution would be to have a CI job that compiles with GCC, to catch these before they're merged.
This isn't the first time this has happened - #1729
Unless shad wants to explicitly drop gcc support, it's good that the environments vary, more testing happens that way.
@tomboylover93 commented on GitHub (Jan 2, 2025):
Since PR #2000 got merged this should be fixed. I've taken the idea of a GCC CI job into consideration and will open a PR for it later.
@Hermiten commented on GitHub (Jan 2, 2025):
Can you try @C0rn3j ? Thanks you :)
@C0rn3j commented on GitHub (Jan 2, 2025):
Compiles, thanks!