-
Notifications
You must be signed in to change notification settings - Fork 559
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
Build fails on physfs: #1167
Labels
Comments
You can unset compliance with C99 in the cmakelists to get past this. Comment out lines 303 and 304 in desktop_version/CMakeLists.txt, produce a clean build directory, then compile. My preferred way:
|
InfoTeddy
added a commit
to InfoTeddy/VVVVVV
that referenced
this issue
Jul 12, 2024
Due to a confluence of weird factors, it turns out that PhysFS is compiling with implicit function definitions due to function definitions that get hidden with -std=c99, but not with -std=gnu99 (or the default GCC value of -std=gnu17). Also, due to a recent GCC update (GCC 14), implicit function declarations are actually prohibited with -std=c99 as the C99 standard proscribes. This meant that people started getting build errors in PhysFS code on default settings, which wasn't ideal. To fix this, we will make our -std= flags apply only to VVVVVV source files. In CMake 2.8.12, this can be done with set_source_files_properties. Additionally the flags to disable exceptions and RTTI are scoped down too. Thanks to leo60228 for helping debug and solve this issue. Fixes TerryCavanagh#1167.
2 tasks
InfoTeddy
added a commit
that referenced
this issue
Jul 13, 2024
Due to a confluence of weird factors, it turns out that PhysFS is compiling with implicit function definitions due to function definitions that get hidden with -std=c99, but not with -std=gnu99 (or the default GCC value of -std=gnu17). Also, due to a recent GCC update (GCC 14), implicit function declarations are actually prohibited with -std=c99 as the C99 standard proscribes. This meant that people started getting build errors in PhysFS code on default settings, which wasn't ideal. To fix this, we will make our -std= flags apply only to VVVVVV source files. In CMake 2.8.12, this can be done with set_source_files_properties. Additionally the flags to disable exceptions and RTTI are scoped down too. Thanks to leo60228 for helping debug and solve this issue. Fixes #1167.
leo60228
pushed a commit
to leo60228/VVVVVV
that referenced
this issue
Oct 10, 2024
Due to a confluence of weird factors, it turns out that PhysFS is compiling with implicit function definitions due to function definitions that get hidden with -std=c99, but not with -std=gnu99 (or the default GCC value of -std=gnu17). Also, due to a recent GCC update (GCC 14), implicit function declarations are actually prohibited with -std=c99 as the C99 standard proscribes. This meant that people started getting build errors in PhysFS code on default settings, which wasn't ideal. To fix this, we will make our -std= flags apply only to VVVVVV source files. In CMake 2.8.12, this can be done with set_source_files_properties. Additionally the flags to disable exceptions and RTTI are scoped down too. Thanks to leo60228 for helping debug and solve this issue. Fixes TerryCavanagh#1167. (cherry picked from commit ff611a5)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Arch Linux with gcc 14.1.1 the build is failing on physfs. When I build physfs alone from it's repo on the same commit it works fine.
The text was updated successfully, but these errors were encountered: