[rcore] Raylib fails to build on gcc 14+

[kwargstar]

Hello there,

I got into raylib today as I'm learning C for fun. However, building raylib from source on GNU/Linux with gcc 14+ produces an error.

My system:

• Linux 6.12 (Fedora Workstation)
• gcc 14.2.1
• raylib commit 08b089f

After cloning the repo, I navigate to raylib/src and run the following:

$ make clean
$ make PLATFORM=PLATFORM_DESKTOP RAYLIB_LIBTYPE=SHARED
gcc -c rcore.c -Wall -D_GNU_SOURCE -DPLATFORM_DESKTOP_GLFW -DGRAPHICS_API_OPENGL_33 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing -std=c99 -fPIC -O1 -Werror=implicit-function-declaration -fPIC -DBUILD_LIBTYPE_SHARED -fvisibility=hidden -D_GLFW_X11  -I.  -Iexternal/glfw/include
rcore.c: In function ‘IsFileExtension’:
rcore.c:1934:34: error: initialization of ‘const char **’ from incompatible pointer type ‘char **’ [-Wincompatible-pointer-types]
 1934 |         const char **checkExts = TextSplit(ext, ';', &extCount); // WARNING: Module required: rtext
      |                                  ^~~~~~~~~
make: *** [Makefile:730: rcore.o] Error 1

It seems the compiler is throwing an error here, but I'm not proficient enough to diagnose it further.

Thanks!

[kwargstar]

Building appears to work using older gcc versions, throwing a warning instead of an error (in my case, I had 8.3 lying around):

$ make -e
gcc -c rcore.c -Wall -D_GNU_SOURCE -DPLATFORM_DESKTOP_GLFW -DGRAPHICS_API_OPENGL_33 -Wno-missing-braces -Werror=pointer-arith -fno-strict-aliasing -std=c99 -fPIC -O1 -Werror=implicit-function-declaration -D_GLFW_X11  -I.  -Iexternal/glfw/include
rcore.c: In function 'IsFileExtension':
rcore.c:1934:34: warning: initialization of 'const char **' from incompatible pointer type 'char **' [-Wincompatible-pointer-types]
         const char **checkExts = TextSplit(ext, ';', &extCount); // WARNING: Module required: rtext
                                  ^~~~~~~~~

Thanks to antediluvianapocalypse on the discord for confirming this behavior with gcc 12 and Clang<16. It seems gcc 14+ and Clang 16+ reject this behavior pertaining to the const char ** vs char **.

[JeffM2501]

Fixed in PR #4680

[raysan5]

@kwargstar thanks for reporting, fixed.

It seems GCC 14+ really messed things up with that error... :(