-
Notifications
You must be signed in to change notification settings - Fork 11
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
GCC 14.2 compilation issues/errors (appstub.mod, io.mod ...) because of now required casts #332
Comments
adding "-Wno-incompatible-pointer-types" removed a lot of the clutter and made it compile".
As it is only available after GCC 5 I am not sure if we need to take care of it with some GCC-Version check ... |
The bbThreadRegister-call n "sdl.mod/SDL/src/thread/SDL_thread.c SDL_Runthread" also does some conversion it does not like.
I supressed it with |
the gnu_source-part is now added via 0ed5db0 debugger-issue resolved and |
So I tried to compile on ArchLinux running a GCC 14.2.
(required an install of webkit2gtk to get MaxIDE running first).
Compiling a simple sample for now:
first error popping up is about some implicit declaration (because it does not find the function)
I simply prepended
#define _GNU_SOURCE
to "brl.mod/appstub.mod/appstub.linux.c" to fix that.next error is something which thrown a lot (I for now stopped trying to "fix" things as I am not sure if it is even correct what I do - or if it just removes the warning but breaks the code :D)
Sample error:
Which I fixes with:
As said similar needs to be done in other files (eg blitz_app.c):
It also affects stuff like physfs (io.mod) - but I think there the error can be fixed differently - there the first element of a char array pointer was tried to be assigned to a char pointer. Without the ampersand C should (according to the internet :D) already return the first element (so a char pointer here):
Is it worth to try "fixing it on my own" or is it not correct what I am doing here?
Maybe just adding the compiler flag to ignore these things should do (plus the #define-line ...)
The text was updated successfully, but these errors were encountered: