GCC Toolchain?

[Wiibuntu]

Ive noticed your old kernels compile under the standard GCC cross compilation toolchain, but now they spit out a ton of errors. I tried using DevKitPro's GCC Toolchain and the kernel builds (with one fixable issue involving gpio.h)

Can you please clarify what GCC toolchain you will be using for the future so anyone building from old kernels wont get confused.

[techflashYT]

DevkitPPC will never work properly. You need to use a standard powerpc-linux-gnu / powerpc-unknown-linux-gnu toolchain.
CrossTool-NG is recommended. See the rudimentary guide for how to use it (https://wiki.wii-linux.org/wiki/Building_Kernel_Guide) for more information.

See the compatibility matrix (https://wiki.wii-linux.org/wiki/Wii-Linux#Compatibility_&_Support_Matrix) as well, to know what kernel versions support what features, if necessary.

[Wiibuntu]

Get this error now using standard GCC powerpc-linux-gnu. Never used to get this compilation error before you made a ton of changes to v4.19.

[Fancy2209]

Get this error now using standard GCC powerpc-linux-gnu. Never used to get this compilation error before you made a ton of changes to v4.19.

Use GCC 14, you can pick by using ct-ng menuconfig before building

[techflashYT]

Actually that may be caused by GCC 14
-mcpu= is ther official way to do that in GCC13, and that's what 4.19 uses.
I can confirm without a doubt that it works on my GCC13 config, as-is specified in the wiki article I linked. If you were using exactly that config, you would not be getting that error. I highly suspect it would explode like that with GCC 14 (or god forbid, GCC 15).

@Fancy2209 please do not make recommendations that would likely make the situation worse.

[Wiibuntu]

Actually that may be caused by GCC 14 -mcpu= is ther official way to do that in GCC13, and that's what 4.19 uses. I can confirm without a doubt that it works on my GCC13 config, as-is specified in the wiki article I linked. If you were using exactly that config, you would not be getting that error. I highly suspect it would explode like that with GCC 14 (or god forbid, GCC 15).

@Fancy2209 please do not make recommendations that would likely make the situation worse.

I am using GCC 14! Going to install GCC 13 onto a separate VM and see if this works. I didn't even think that GCC 14 could've been the issue.

[Fancy2209]

Actually that may be caused by GCC 14 -mcpu= is ther official way to do that in GCC13, and that's what 4.19 uses. I can confirm without a doubt that it works on my GCC13 config, as-is specified in the wiki article I linked. If you were using exactly that config, you would not be getting that error. I highly suspect it would explode like that with GCC 14 (or god forbid, GCC 15).

@Fancy2209 please do not make recommendations that would likely make the situation worse.

I remembered using 14 when I had to compile the kernel but if was very likely 13, my bad!

[Wiibuntu]

Actually that may be caused by GCC 14 -mcpu= is ther official way to do that in GCC13, and that's what 4.19 uses. I can confirm without a doubt that it works on my GCC13 config, as-is specified in the wiki article I linked. If you were using exactly that config, you would not be getting that error. I highly suspect it would explode like that with GCC 14 (or god forbid, GCC 15).
@Fancy2209 please do not make recommendations that would likely make the situation worse.

I remembered using 14 when I had to compile the kernel but if was very likely 13, my bad!

I too used to use 14 with zero issues. Idk what could've changed.

[techflashYT]

I've never bothered trying with 14, but it really shouldn't even be attempted. GCC 14 is far too new for kernel 4.19. Maybe it'd work better with later kernels once they're ready, but for 4.19 (and very likely under it as well), GCC 13 is the latest you can use.

[Wiibuntu]

This was the issue. GCC 14 is not fully working with some kernels. Not sure why, but using GCC 13 and G++ 13 fixed the issues.

Look forward to future kernels.