yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] tr4ne88:
Compiling error

Hi, I followed your guide but I'm stucked with the compiling...

I wanted to build a kernel for my Samsung Galaxy S9+ (G965F) but when I type the command "make exynos_defconfig" (the config file of my phone) it gives me some error...

Here it is:

[COLOR="Red"]root@kali[/COLOR]:[COLOR="Blue"]~/Kernel2/S9[/COLOR]# make exynos_defconfig
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
In file included from [B]scripts/kconfig/zconf.tab.c:2576[/B]:
[B]scripts/kconfig/confdata.c[/B]: In function ‘conf_write’:
[B]scripts/kconfig/confdata.c:773:19[/B]: [COLOR="DarkOrchid"]warning[/COLOR]: ‘[B]%s[/B]’ directive writing likely 7 or more bytes into a re
gion of size between 1 and 4097 [[COLOR="DarkOrchid"]-Wformat-overflow=[/COLOR]]
773 | sprintf(newname, [COLOR="darkorchid"]"%s%s"[/COLOR], dirname, basename);
| [COLOR="darkorchid"]^~~~~~[/COLOR]
[B]scripts/kconfig/confdata.c:773:19[/B]: [COLOR="DeepSkyBlue"]note[/COLOR]: assuming directive output of 7 bytes
[B]scripts/kconfig/confdata.c:773:2:[/B] [COLOR="deepskyblue"]note[/COLOR]: [B]‘sprintf’[/B] output 1 or more bytes (assuming 4104) into a des
tination of size 4097
773 | [COLOR="DeepSkyBlue"]sprintf(newname, "%s%s", dirname, basename)[/COLOR];
| [COLOR="deepskyblue"]^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~[/COLOR]
[B]scripts/kconfig/confdata.c:776:20[/B]: [COLOR="darkorchid"]warning[/COLOR]:[B] ‘.tmpconfig.’[/B] directive writing 11 bytes into a region
of size between 1 and 4097 [[COLOR="darkorchid"]-Wformat-overflow=[/COLOR]]
776 | sprintf(tmpname, [COLOR="darkorchid"]"%s.tmpconfig.%d"[/COLOR], dirname, (int)getpid());
| [COLOR="DarkOrchid"] ^~~~~~~~~~~~~~~~~[/COLOR]
[B]scripts/kconfig/confdata.c:776:3:[/B] [COLOR="deepskyblue"]note[/COLOR]:[B] ‘sprintf’[/B] output between 13 and 4119 bytes into a destinati
on of size 4097
776 | [COLOR="deepskyblue"]sprintf(tmpname, "%s.tmpconfig.%d", dirname, (int)getpid());[/COLOR]
| [COLOR="DeepSkyBlue"]^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~[/COLOR]
HOSTLD scripts/kconfig/conf
Kconfig:15:warning: environment variable ANDROID_MAJOR_VERSION undefined
drivers/leds/Kconfig:686:warning: ignoring type redefinition of 'LEDS_KTD2692' from 'tristate' to 'boolean'
fs/sdcardfs//Kconfig:5: recursive inclusion detected. Inclusion path:
current file : 'fs/sdcardfs//Kconfig'
included from: 'fs/sdcardfs//Kconfig:7'
make[1]: *** [scripts/kconfig/Makefile:112: exynos_defconfig] Error 1
make: *** [Makefile:570: exynos_defconfig] Error 2

I followed all the steps but I'm getting always the same error... I don't know what to do. I need some help please :(

ps: I downloaded the kernel source from the samsung site
[Android Software/Hacking General [Developers Only]] ezzony:
Well I see .ko files are created in the final output on what I'm currently working on but I don't know if this means they were or weren't built into the kernel.

Is this the relevant section in the config file? If so do you know what the other options mean?

CONFIG_MODULES=y

CONFIG_MODULE_UNLOAD=y

CONFIG_MODULE_FORCE_UNLOAD=y

CONFIG_MODVERSIONS=y

CONFIG_MODULE_SIG=y

CONFIG_MODULE_SIG_FORCE=y

CONFIG_MODULE_SIG_SHA512=y

edit: the problem I'm having is that I'm compiling stock source with the original cross compiler , no changes at all, but the touchscreen doesn't work and I'm wondering if it has something to do with modules.
[Android Software/Hacking General [Developers Only]] nathanchance:
Helping you boot a kernel is outside the scope of this thread. Please find your device specific forum and ask there.

It seems like a broken kernel source but I don't know, that should not be happening with the stock source. The ANDROID_MAJOR_VERSION thing might be necessary.

Yes, you can remove those and see if it helps. It most likely is related. I know that for the Pixel 2, that was the case. We had to build the touchscreen driver into the kernel image instead of as a module.
[Android Software/Hacking General [Developers Only]] Soul Spark:
Since there are no forums regarding kernel development for this device so I thought a little help would be greatly appreciated, like are these https://pastebin.com/SKttwX3y warnings might be the cause for it?
[Android Software/Hacking General [Developers Only]] ezzony:
No luck. I wonder if there is anything else I could be doing wrong?

I put the Image.gz-dtb file into an anykernel zip and the other way by extracting boot.img. I can see using a mouse attached to the device to navigate that my new kernel has been installed using a kernel manager app.

If anyone could suggest something else to try I'm be greatful as I'm completely stuck on this.

Oh, btw, should I delete the .ko files in /system/lib/modules when the .ko files are built into the kernel. And if I don't build them into the kernel should I replace them with the newly created ones erasing the stock ones in the same directory?
[Android Software/Hacking General [Developers Only]] nathanchance:
No, just disabling MODULES is enough because the kernel won't have the loading support.

Unfortunately, I do not have much else to offer you :(
[Android Software/Hacking General [Developers Only]] ValKyre:
bro., i try compile pixel 2.

it finish... but it only work for stock source. (4.4.200)

when i use source wahoo (your work) - 4.4.219 after i flash... it boot but display freeze. (it happen same with stock source i try uptream 200 to 219 by merge ur linux update).

.

how can i fix that ? hope u can give some free time help me...!
[Android Software/Hacking General [Developers Only]] sdeft:
[MENTION=6842057]nathanchance[/MENTION]

I hope you are well. I was wondering. Have you seen the below messages before ?

depmod: WARNING: could not open modules.order at /build/havoc/out/target/product/ginkgo/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0: No such file or directory

depmod: WARNING: could not open modules.builtin at /build/havoc/out/target/product/ginkgo/obj/PACKAGING/depmod_vendor_intermediates/lib/modules/0.0: No such file or directory

They appear after the kernel build in the rom build process.
[Android Software/Hacking General [Developers Only]] Keskebeu:
Warnings are treated as errors in kernel build.

Open your Makefile: nano Makefile in your kernel directory. Scroll down to here :

CFLAGS_MODULE =

AFLAGS_MODULE =

LDFLAGS_MODULE =

CFLAGS_KERNEL	=

AFLAGS_KERNEL	=

Add -w flag so it looks like this:

CFLAGS_MODULE = -w

Add -w to all but LDFLAGS.

Scroll down little more and add the -w flag again to:

KBUILD_CFLAGS := -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs \

-fno-strict-aliasing -fno-common \

-Werror-implicit-function-declaration \

-Wno-format-security \

-fno-delete-null-pointer-checks \

-w

Hope this helps.
[Android Software/Hacking General [Developers Only]] ezzony:
I managed to fix the touchscreen issue and can stop pulling my hair out now. I used Linaro gcc instead and that fixed the issue.

But on the issue of compiler versions is it 'better' to use a more recent version. Later version don't work for me. Is there a way to make it work. Is there a benefit in terms of performance in any case? edit: I see now in your OP that I need to patch my kernel source, but is it worth the trouble in terms of performance.
[Android Software/Hacking General [Developers Only]] nathanchance:
Yes, it is generally better to use more recent compiler versions. You get access to new warnings that can find latent bugs in your code and each compiler releases typically fixes latent bugs within the compiler as well.

It is up to you though, it is all about the gains versus the effort you have to put in to getting it to work.
[Android Software/Hacking General [Developers Only]] tripLr:
How do we use / activate linero gcc in a build process ?
[Android Software/Hacking General [Developers Only]] ezzony:
That's a question for the experts. I didn't do anything, it just worked.
[Android Software/Hacking General [Developers Only]] ghiffaryr:
Important suggestion

Much thanks for you to teach us about this. But, the command not fully working. You need to revised that to :

mkdir -p out

make clean

make mrproper

make O=out <defconfig_name>

make O=out -j$(nproc --all)

Thanks. :good:
[Android Software/Hacking General [Developers Only]] Jaernyx:
Full disclosure; I'm extremely new to this and still trying to learn. I apologize if this is a dumb question, however

I'm trying to compile a kernel source using your steps, and everything seems to go okay until the make defconfig step, I've attached an attachment of my process and error. Hopefully this is something easy I'm overlooking.

Thanks for any assistance! I apologize for my ignorance. :)
[Android Software/Hacking General [Developers Only]] Delevoper:
start developementing

I started development on my smartphone, have kernel source and want compile to use lineage. Is mtk device, follow this guide i can do this?
[Android Software/Hacking General [Developers Only]] Zzla:
Thanks for good tutorial . I succeeded compiling of oneplus6 official kernel.
[Android Software/Hacking General [Developers Only]] twfs:
Hi I am trying to build for a moto g7 power and continue to get this error and have no idea how to fix so any help would be appreciated.

CC drivers/base/module.o

CC drivers/base/soc.o

CC drivers/base/pinctrl.o

LD drivers/base/built-in.o

CC drivers/block/brd.o

CC drivers/block/loop.o

CC drivers/block/zram/zcomp.o

CC drivers/block/zram/zram_drv.o

LD drivers/block/zram/zram.o

LD drivers/block/zram/built-in.o

LD drivers/block/built-in.o

CC drivers/bluetooth/bluetooth-power.o

CC drivers/bluetooth/btfm_slim.o

drivers/bluetooth/btfm_slim.c:26:10: fatal error: btfm_slim.h: No such file or directory

#include <btfm_slim.h>

^~~~~~~~~~~~~

compilation terminated.

make[2]: *** [scripts/Makefile.build:340: drivers/bluetooth/btfm_slim.o] Error 1

make[1]: *** [scripts/Makefile.build:653: drivers/bluetooth] Error 2

make: *** [Makefile:1108: drivers] Error 2
[Android Software/Hacking General [Developers Only]] nathanchance:
You need to use 'make O=out' for all invocations of 'make'.
[Android Software/Hacking General [Developers Only]] Oswald Boelcke:
[MENTION=6842057]nathanchance[/MENTION] Congratulations to your new wings! The title suits you well and is definitely well deserve!

Stay safe and stay healthy!

Regards

Oswald Boelcke
[Android Software/Hacking General [Developers Only]] twfs:
Thank you for the reply. I tried that a couple of times already because I had read that on the first page but I probably wasn't doing something right. Will hopefully get a chance to try again tomorrow and will let you know how it goes. Thanks again
[Android Software/Hacking General [Developers Only]] physwizz:
[MENTION=6842057]nathanchance[/MENTION]

I have experience in other areas but

I'm a noob at kernel building

I downloaded the cross-compiler

I downloaded the source code tarball and expanded

Then followed the instructions

Got up to

Make clean

I get this message

make: *** No rule to make target 'clean'. Stop.
[Android Software/Hacking General [Developers Only]] nathanchance:
You do not need to run 'make clean' if you have not actually built anything.
[Android Software/Hacking General [Developers Only]] physwizz:
Thanks
[Android Software/Hacking General [Developers Only]] physwizz:
Sorry to bug you but now I get this

grahame@grahame-VirtualBox:~/Downloads/Kernel$ make O=out exynos7885-a20dv_defconfig

make[1]: Entering directory '/home/grahame/Downloads/Kernel/out'

HOSTCC scripts/basic/fixdep

GEN ./Makefile

HOSTCC scripts/kconfig/conf.o

HOSTCC scripts/kconfig/zconf.tab.o

In file included from ../scripts/kconfig/zconf.tab.c:2576:

../scripts/kconfig/confdata.c: In function ‘conf_write’:

../scripts/kconfig/confdata.c:771:19: warning: ‘%s’ directive writing likely 7 or more bytes into a region of size between 1 and 4097 [-Wformat-overflow=]

771 | sprintf(newname, "%s%s", dirname, basename);

| ^~~~~~

../scripts/kconfig/confdata.c:771:19: note: assuming directive output of 7 bytes

In file included from /usr/include/stdio.h:867,

from ../scripts/kconfig/zconf.tab.c:84:

/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output 1 or more bytes (assuming 4104) into a destination of size 4097

36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,

| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

37 | __bos (__s), __fmt, __va_arg_pack ());

| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In file included from ../scripts/kconfig/zconf.tab.c:2576:

../scripts/kconfig/confdata.c:774:20: warning: ‘.tmpconfig.’ directive writing 11 bytes into a region of size between 1 and 4097 [-Wformat-overflow=]

774 | sprintf(tmpname, "%s.tmpconfig.%d", dirname, (int)getpid());

| ^~~~~~~~~~~~~~~~~

In file included from /usr/include/stdio.h:867,

from ../scripts/kconfig/zconf.tab.c:84:

/usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output between 13 and 4119 bytes into a destination of size 4097

36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,

| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

37 | __bos (__s), __fmt, __va_arg_pack ());

| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

HOSTLD scripts/kconfig/conf

Kconfig:15:warning: environment variable ANDROID_MAJOR_VERSION undefined

fs/sdcardfs//Kconfig:5: recursive inclusion detected. Inclusion path:

current file : 'fs/sdcardfs//Kconfig'

included from: 'fs/sdcardfs//Kconfig:7'

make[2]: *** [../scripts/kconfig/Makefile:110: exynos7885-a20dv_defconfig] Error 1

make[1]: *** [/home/grahame/Downloads/Kernel/Makefile:563: exynos7885-a20dv_defconfig] Error 2

make[1]: Leaving directory '/home/grahame/Downloads/Kernel/out'

make: *** [Makefile:150: sub-make] Error 2

I may be in the wrong folders when I run commands

I did this first.

Was this the correct folder for these commands?

grahame@grahame-VirtualBox:~/aarch64-linux-android-4.9$ export CROSS_COMPILE=$(pwd)/bin/aarch64-linux-android-

grahame@grahame-VirtualBox:~/aarch64-linux-android-4.9$ export ARCH=arm64 && export SUBARCH=arm64
[Android Software/Hacking General [Developers Only]] nathanchance:
I know that ANDROID_MAJOR_VERSION is a Samsung specific thing... I am not sure beyond that unfortunately. That is probably the source of your issue but I am not sure. Are you trying to compile a stock or custom kernel?
[Android Software/Hacking General [Developers Only]] physwizz:
Computing has been my hobby since 1983 when I got my first pc but I've never managed to build a kernel.

Lately I've been supporting the Galaxy a20 community with various guides here

https://xdaforums.com/galaxy-a20/how-to

By building a kernel I will both develop a new skill and help out another a20 user who desperately needs an overclocked custom Android 9 kernel for gaming.

I thought I might start with a stock Q kernel and then move on to overclocked custom kernel.

I'm working in a Ubuntu virtual box on my iMac.

I have downloaded the cross-compiler and unpacked the source code tarball.

I'm now trying to produce a kernel from this but I'm not sure of which folder to be in when i run your linux commands or weather I need to edit one if the files.
[Android Software/Hacking General [Developers Only]] zaduma:
Well, first, thank you for this guide.

I'm having a little problem, under /arch/arm64/configs/ I see 15 different defconfig files.

13 are letters and numbers i.e. evb6771_64_emmc_mhl_debug_defconfig

with most having a matching non debug i.e. evb6771_64_emmc_mhl_defconfig

the other three are simply named cuttlefish_defconfig, defconfig, and ranchu64_defconfig

I'm pretty unsure of where to go from here and how to know which one is the proper one for my device. (ZTE Blade A3 Prime Z5157V) None of the files have 5157 in the name, and my phone is currently soft bricked until I advance this project :/

Edit: Before posting I think I realized that building the kernel won't help me get recovery.img :( But I am in this deep, so I might as well build the kernel.

Any help is appreciated!
[Android Software/Hacking General [Developers Only]] Forenche:
Simple and well explained guide. Really appreciate the hardwork. Thank you :)
[Android Software/Hacking General [Developers Only]] HafidzRadhival:
how do I add features in the custom kernel that I made?
[Android Software/Hacking General [Developers Only]] Vertigorg:
Hey, thanks for the useful guide.

It seems that the pre-built google toolchain you have referenced seems obsolete, you can see that in commit fc97ce6 they have removed the gcc binary from the source tree.

Of course I could just checkout the commit before that, but I was wondering if there is a better/newer pre-built toolchain and you just forgot to update the thread?

Update: It seems that GCC was indeed deprecated by androidhttps://android.googlesource.com/platform/prebuilts/clang/host/linux-x86/+/master/GCC_4_9_DEPRECATION.md.

Should we switch to clang too?

Also, I could not find information regarding this anywhere else, I'm compiling a custom kernel (hasty) for my device (davinci) because I'm patching in wireguard kernel support. I was wondering If I need to take an extra step to link the kernel to the device specific vendor drivers? Or is this step already done by the custom kernel maintainer?

On the kernel thread (https://xdaforums.com/mi-9t/development/kernel-hasty-t4084863) it claims to support any ROM using the MIUI vendor
[Android Software/Hacking General [Developers Only]] Hari Nguyen:
You can still using gcc (using Clang require some addition work) by checkout ndk-26-release branch or lower than 26 depend on your android version, maybe new android did complie with Clang by default but I don't have any info on that

---------- Post added at 12:06 PM ---------- Previous post was at 11:56 AM ----------

Just wonder, can I use drivers folder from other device with same chipset that I have (maybe copy and replace) to compile the kernel. I come to this idea because the drivers folder of my device is so messup with wrong #include here and the

(Edited: not work)
[Android Software/Hacking General [Developers Only]] Hari Nguyen:
I have similar problem as you have and I think it has something to do with the source code because if you run find in kernel folder and grep for that header file it did exists but the file using it include it with wrong path
[Android Software/Hacking General [Developers Only]] palmbeach05:
You do know you can edit your posts and do the deleting of stuff on your own, right?
[Android Software/Hacking General [Developers Only]] dps910:
Hi, I have successfully built my kernel, but I am having trouble booting any of the files in /out/arch/arm/boot. Here is what I have done to compile my kernel

git clone https://github.com/LineageOS/android_kernel_motorola_msm8916
cd android_kernel_motorola_msm8916
mkdir out
make O=out msm8916_defconfig
make O=out menuconfig
make O=out -j8

I now have some files in /out/arch/arm/boot. zImage, Image and zImage-dtb. I try to do

fastboot boot

on all of them. None of them are booting, and I get these errors with adb -d logcat htt ps://hasteb .in/rewelicu.yaml. I was told that zImage-dtb is the kernel, but I am not sure if I would replace

boot.img-zImage

with zImage, Image or zImage-dtb and none of them work anyway. Have I done something wrong? I am not sure.
[Android Software/Hacking General [Developers Only]] santiagonbl:
1-To use "fastboot boot" you have to build the entire boot image (boot.img, basically kernel+ramdisk).

2- When you build a kernel, AnyKernel3 (You can find it in osm0sis git) is the best and easiest option to create a flasheable zip.
[Android Software/Hacking General [Developers Only]] Alif Ilhan:
Hello.....

I want to develop a custom kernel for a MediaTek based device (MT6582). Thankfully the kernel source was released which contained the board files and the drivers for that specific device. I also have seen other refference board file kernel and now I know where and how to place the board files(mach-mt6582/, include/, drivers/, net/) But the problem is the kernel version is very old (3.4.67) and I am scared that board drivers will not work. Can you suggest me how to solve this issue? Or can you tell me if there is an EASY way to port old kernel drivers to a new kernel( I have seen this type of work but those involve by-hand code editing which is really not easy. But I also don't mind this device getting bricked)

Thanks in advance,

Alif
[Android Software/Hacking General [Developers Only]] jbm76:
Wifi isn't working on my Oneplus 6 after flashing a 10.0 kernel I compiled myself for the first time. Is there a driver that needs to be enabled?

EDIT- I enabled the wlan in make menuconfig but when I copied my .config file to a custom deconfig file it wouldn't compile without errors. It would only compile if I used sdm845-perf_defconfig.

It gives me this error when I try to build it.

export CROSS_COMPILE=$(pwd)/bin/aarch64-linux-android-

export ARCH=arm64 && export SUBARCH=arm64

make O=out clean

make O=out mrproper

make O=out macka_defconfig

It gives these warnings

boot/config-5.4.0-45-generic:724:warning: symbol value 'm' invalid for KVM

/boot/config-5.4.0-45-generic:1571:warning: symbol value 'm' invalid for NET_DSA_TAG_BRCM

/boot/config-5.4.0-45-generic:1574:warning: symbol value 'm' invalid for NET_DSA_TAG_DSA

/boot/config-5.4.0-45-generic:1575:warning: symbol value 'm' invalid for NET_DSA_TAG_EDSA

/boot/config-5.4.0-45-generic:1578:warning: symbol value 'm' invalid for NET_DSA_TAG_QCA

/boot/config-5.4.0-45-generic:1581:warning: symbol value 'm' invalid for NET_DSA_TAG_TRAILER

/boot/config-5.4.0-45-generic:3938:warning: symbol value 'm' invalid for JOYSTICK_IFORCE_USB

/boot/config-5.4.0-45-generic:3939:warning: symbol value 'm' invalid for JOYSTICK_IFORCE_232

/boot/config-5.4.0-45-generic:4561:warning: symbol value 'm' invalid for GPIO_MB86S7X

/boot/config-5.4.0-45-generic:5663:warning: symbol value 'm' invalid for RADIO_SI470X

/boot/config-5.4.0-45-generic:6293:warning: symbol value 'm' invalid for FB_BACKLIGHT

/boot/config-5.4.0-45-generic:8245:warning: symbol value 'm' invalid for ASHMEM

/boot/config-5.4.0-45-generic:9205:warning: symbol value 'm' invalid for ANDROID_BINDER_IPC

/boot/config-5.4.0-45-generic:9272:warning: symbol value 'm' invalid for SLIMBUS

make O=out DTC_EXT=dtc CONFIG_BUILD_ARM64_DT_OVERLAY=y -j$(nproc --all)

Using .. as source for kernel

.. is not clean, please run 'make mrproper'

in the '..' directory.

make[1]: *** [/home/macka/Desktop/android-kernel/ncop6/Makefile:1158: prepare3] Error 1

make[1]: Leaving directory '/home/macka/Desktop/android-kernel/ncop6/out'

make: *** [Makefile:152: sub-make] Error 2
[Android Software/Hacking General [Developers Only]] Anon333266:
Hi [MENTION=6842057]nathanchance[/MENTION]

I have a Mi 9T Pro (Raphael) and I want to start building kernels for my device.

It has an Snapdragon 855 (sm8150).

I downloaded the source from Xiaomi (https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/raphael-p-oss)

I also wanted to download CAF Tags for this kernel and integrate it, but I don't know what to choose.

It has several sm8150 CAF Tags but different chipsets.

How do I download properly from CodeAurora?

I tried your tutorial it compiles with no error but I can't find an image.

When I try it again it gives different errors in different trys.

I tried GCC, Clang and Proton Clang with several sources.

I can't find any help at the internet.

I can give further error codes and pictures, but I don't know if this thread is still active.

Please answer in this thread if you still have time to help.

Thanks in advance.