nathanchance / android-kernel-clang Goto Github PK

Google GCC is removed from the repo, now this repo only contains the OWNERS file. can you please update the steps for compiling the Kernel, thanks.

Can I apply the patches you provided in the readme file to a 4.14.117 kernel or it would have lots of conflicts?
Can you provide all of these patches in one patch file?
Do these patches work with Qualcomm llvm?

The correct one is this

problem showed like this.
Is it clang version to blame?

https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/1294370

looks like an interesting commit to link to.

Hi there：
I tried to build the floral_defconfig （from my understanding is used for coral and flame）
Everything seems going well when following your guide “How to compile the kernel with Clang (standalone)".

Unfortunately I got a error as below:
aarch64-linux-android-ld.gold: error: LLVMgold.so: could not load plugin library: LLVMgold.so: cannot open shared object file: No such file or directory
../scripts/Makefile.build:613: recipe for target 'arch/arm64/lib/lib-ksyms.o' failed
make[2]: *** [arch/arm64/lib/lib-ksyms.o] Error 1
/home/dongtaotao/msm/Makefile:1153: recipe for target 'arch/arm64/lib' failed
make[1]: *** [arch/arm64/lib] Error 2

Would you mind let me know anything I need to check?

Hey, thanks for the guidelines for clang. But I still don't no what commits I need to choose for the OnePlus 7 pro kernel.
Maybe you can help me.
Here is my fork : https://github.com/Flashaholicturbo/android_kernel_oneplus_sm8150

Can't find the 3.18.y kernel patch ，i don't know where to find about that, could you tell me？

After applying clang patches, I decicded to first do an regular GCC4 build to sort out issues with the patches. Well, I got a kernel panic about accessing userspace memory after it tried to play the touch sound. After way to much debugging, I found the problematic patch:
n4archive/OptimKernel@da944ad
I tried this alternative commit:
n4archive/OptimKernel@fd1ac4e
It doesn't crash anymore, but sound remains silent. Completely.
(I still use GCC 4!)
Without any of those 2 patches, it's fine again. No crash and no silence.

Well, how to properly fix the warning?

Hi Nathan,

May I ask a question about compilation other version of android kernel?

Followed by this tutorial, I can successfully compile android-4.4 and android-4.9. However, Is it possible to compile any versions of android kernel(eg., 4.10.0) if I properly add the Clang commits to this kernel source ?

Best,
Yue

Thanks for providing such cool tutorial! However, I encounter a problem in linking process. It says undefined reference to stpcpy. Then, I search stpcpy in the android source code, I did not see any definition. I have been stuck for the whole day, could you give some hints if possible?

  CC [M]  drivers/scsi/st.o
  LD [M]  drivers/net/wireless/realtek/rtlwifi/rtlwifi.o
  LD [M]  drivers/net/wireless/realtek/rtlwifi/rtl_pci.o
  CC [M]  drivers/net/wireless/realtek/rtlwifi/rtl8723be/sw.o
  CC [M]  drivers/net/wireless/realtek/rtlwifi/rtl8723be/table.o
  LD [M]  drivers/net/wireless/realtek/rtlwifi/rtl_usb.o
  CC [M]  drivers/net/wireless/realtek/rtlwifi/rtl8723be/trx.o
  CC [M]  drivers/scsi/ch.o
  CC [M]  drivers/scsi/ses.o
  CC [M]  drivers/scsi/scsi_debug.o
  LD [M]  drivers/net/wireless/realtek/rtlwifi/rtl8821ae/rtl8821ae.o
  LD      drivers/scsi/scsi_mod.o
  LD      drivers/scsi/sd_mod.o
  LD      drivers/scsi/sr_mod.o
  LD [M]  drivers/net/wireless/realtek/rtlwifi/rtl8723be/rtl8723be.o
  LD      drivers/net/wireless/built-in.o
  LD      drivers/net/built-in.o
  LD [M]  drivers/scsi/qla2xxx/qla2xxx.o
  LD      drivers/scsi/built-in.o
  LD      drivers/built-in.o
  GEN     .version
  LD      vmlinux.o
  MODPOST vmlinux.o
  CHK     include/generated/compile.h
  UPD     include/generated/compile.h
  CC      init/version.o
  LD      init/built-in.o
drivers/built-in.o: In function `devspec_show':
/home/yuexiao/Documents/research/diffcvss/LLVM/andoid_mainline/kernel_common/out/../drivers/pci/pci-sysfs.c:440: undefined reference to `stpcpy'
drivers/built-in.o: In function `tty_line_name':
/home/yuexiao/Documents/research/diffcvss/LLVM/andoid_mainline/kernel_common/out/../drivers/tty/tty_io.c:1360: undefined reference to `stpcpy'
/home/yuexiao/Documents/research/diffcvss/LLVM/andoid_mainline/kernel_common/out/../drivers/tty/tty_io.c:1360: undefined reference to `stpcpy'
/home/yuexiao/Documents/research/diffcvss/LLVM/andoid_mainline/kernel_common/out/../drivers/tty/tty_io.c:1360: undefined reference to `stpcpy'
drivers/built-in.o: In function `get_ata_class_names':
/home/yuexiao/Documents/research/diffcvss/LLVM/andoid_mainline/kernel_common/out/../drivers/ata/libata-transport.c:149: undefined reference to `stpcpy'
security/built-in.o:/home/yuexiao/Documents/research/diffcvss/LLVM/andoid_mainline/kernel_common/out/../security/apparmor/lsm.c:818: more undefined references to `stpcpy' follow
make[1]: *** [/home/yuexiao/Documents/research/diffcvss/LLVM/andoid_mainline/kernel_common/Makefile:1071: vmlinux] Error 1
make[1]: Leaving directory '/home/yuexiao/Documents/research/diffcvss/LLVM/andoid_mainline/kernel_common/out'
make: *** [Makefile:152: sub-make] Error 2

Hi

I am getting the following error after compiling the kernel using the mentioned steps

./drivers/firmware/efi/libstub/lib.a(arm64-stub.stub.o): In function __efistub_handle_kernel_image': __efistub_arm64-stub.c:(.init.init.text+0x1c): undefined reference to __efistub___stack_chk_guard'
__efistub_arm64-stub.c:(.init.init.text+0x20): undefined reference to __efistub___stack_chk_guard' __efistub_arm64-stub.c:(.init.init.text+0x1d0): undefined reference to __efistub___stack_chk_guard'
__efistub_arm64-stub.c:(.init.init.text+0x1d8): undefined reference to __efistub___stack_chk_guard' __efistub_arm64-stub.c:(.init.init.text+0x21c): undefined reference to __efistub___stack_chk_fail'
./drivers/firmware/efi/libstub/lib.a(arm-stub.stub.o): In function __efistub_efi_open_volume': __efistub_arm-stub.c:(.init.text+0x14): undefined reference to __efistub___stack_chk_guard'
__efistub_arm-stub.c:(.init.text+0x18): undefined reference to __efistub___stack_chk_guard' __efistub_arm-stub.c:(.init.text+0xa0): undefined reference to __efistub___stack_chk_guard'
__efistub_arm-stub.c:(.init.text+0xa8): undefined reference to __efistub___stack_chk_guard' __efistub_arm-stub.c:(.init.text+0xd0): undefined reference to __efistub___stack_chk_fail'
./drivers/firmware/efi/libstub/lib.a(arm-stub.stub.o): In function __efistub_efi_file_size': __efistub_arm-stub.c:(.init.text+0x11c): undefined reference to __efistub___stack_chk_guard'
__efistub_arm-stub.c:(.init.text+0x120): undefined reference to __efistub___stack_chk_guard' __efistub_arm-stub.c:(.init.text+0x258): undefined reference to __efistub___stack_chk_guard'
__efistub_arm-stub.c:(.init.text+0x260): undefined reference to __efistub___stack_chk_guard' __efistub_arm-stub.c:(.init.text+0x2b8): undefined reference to __efistub___stack_chk_fail'
./drivers/firmware/efi/libstub/lib.a(arm-stub.stub.o): In function __efistub_efi_entry': __efistub_arm-stub.c:(.init.text+0x2f0): undefined reference to __efistub___stack_chk_guard'
__efistub_arm-stub.c:(.init.text+0x2f4): undefined reference to __efistub___stack_chk_guard' __efistub_arm-stub.c:(.init.text+0x388): undefined reference to __efistub___stack_chk_guard'
__efistub_arm-stub.c:(.init.text+0x390): undefined reference to __efistub___stack_chk_guard' __efistub_arm-stub.c:(.init.text+0x618): undefined reference to __efistub___stack_chk_fail'
./drivers/firmware/efi/libstub/lib.a(random.stub.o): In function __efistub_efi_get_random_bytes': __efistub_random.c:(.init.text+0x10): undefined reference to __efistub___stack_chk_guard'
__efistub_random.c:(.init.text+0x14): undefined reference to __efistub___stack_chk_guard' __efistub_random.c:(.init.text+0x6c): undefined reference to __efistub___stack_chk_guard'
__efistub_random.c:(.init.text+0x74): undefined reference to __efistub___stack_chk_guard' __efistub_random.c:(.init.text+0x94): undefined reference to __efistub___stack_chk_fail'
./drivers/firmware/efi/libstub/lib.a(random.stub.o): In function __efistub_efi_random_alloc': __efistub_random.c:(.init.text+0xb0): undefined reference to __efistub___stack_chk_guard'
__efistub_random.c:(.init.text+0xb4): undefined reference to __efistub___stack_chk_guard' __efistub_random.c:(.init.text+0x1d8): undefined reference to __efistub___stack_chk_guard'
__efistub_random.c:(.init.text+0x1e0): undefined reference to __efistub___stack_chk_guard' __efistub_random.c:(.init.text+0x260): undefined reference to __efistub___stack_chk_fail'
./drivers/firmware/efi/libstub/lib.a(efi-stub-helper.stub.o): In function __efistub_efi_printk': __efistub_efi-stub-helper.c:(.init.text+0x20): undefined reference to __efistub___stack_chk_guard'
__efistub_efi-stub-helper.c:(.init.text+0x24): undefined reference to __efistub___stack_chk_guard' __efistub_efi-stub-helper.c:(.init.text+0x80): undefined reference to __efistub___stack_chk_guard'

Then I commented out the CONFIG_CC_STACKPROTECTOR_STRONG=y in config file, compilation is successful , Is it okay to do that? any implications from that?

Hello, as mentioned in the title of this issue, I'm trying to figure this out. And I believe as a precondition, I have to use clang on building android kernel. That's why I come here and query if you guys have the similar interest as me :)

This repo is pretty cool! However, I still have some problems when I compile msm-4.9-android-10.
The first command runs pretty well: make O=out oldconfig ARCH=arm64 -Werror
But I encounter a problem when I run:

PATH="/home/yuexiao/Documents/research/diffcvss/LLVM/latest_clang/tc-build/install/bin:/home/yuexiao/Documents/research/diffcvss/LLVM/aarch64-linux-android-4.9/bin:${PATH}" \
make -j$(nproc --all) O=out \
                      ARCH=arm64 \
                      CC=clang \
                      CLANG_TRIPLE=aarch64-linux-gnu- \
                      CROSS_COMPILE=aarch64-linux-android- \
                      CROSS_COMPILE_ARM32=arm-linux-androideabi-

It said ../security/apparmor/crypto.c:37:8: error: fields must have a constant size: I am pretty new to complie Android Kernel with Clang. Any response wil be appreciated!!

CC [M]  fs/ceph/mds_client.o
  CC      security/apparmor/lsm.o
  GEN     security/apparmor/rlim_names.h
  CC      security/apparmor/sid.o
  CC [M]  fs/cifs/file.o
  CC [M]  fs/btrfs/root-tree.o
  CC      security/apparmor/file.o
  CC [M]  fs/coda/file.o
  CC [M]  fs/ceph/mdsmap.o
  CC      security/apparmor/crypto.o
  CC [M]  fs/coda/upcall.o
  CC [M]  fs/btrfs/dir-item.o
../security/apparmor/crypto.c:37:8: error: fields must have a constant size: 'variable length array in structure' extension will never be supported
                char ctx[crypto_shash_descsize(apparmor_tfm)];
                     ^
1 error generated.
make[4]: *** [../scripts/Makefile.build:335: security/apparmor/crypto.o] Error 1
make[4]: *** Waiting for unfinished jobs....
  CC [M]  fs/btrfs/file-item.o
make[3]: *** [../scripts/Makefile.build:648: security/apparmor] Error 2
make[2]: *** [/home/yuexiao/Documents/research/diffcvss/LLVM/andoid_mainline/kernel_common/Makefile:1090: security] Error 2
make[2]: *** Waiting for unfinished jobs....
  CC [M]  fs/btrfs/inode-item.o
  CC [M]  fs/ceph/strings.o
  CC [M]  fs/coda/coda_linux.o
  CC [M]  fs/ceph/ceph_frag.o
  CC [M]  fs/btrfs/inode-map.o

Hi Nathan,

i tried to follow steps mentioned and tried to build Kernel with Clang and im getting build error related to Linker
attaching the snapshot and make command from log

error log and Make command
https://pastebin.com/K5kXM606

can you please help me to fix this issue

thanks and Regards,
Pruthvi

Hi! I am trying to fix various warnings on my kernel and am currently compiling with proton clang. If I use GCC4 together with clang, it compiles just fine. If I however use https://github.com/arter97/arm64-gcc (GCC 10) with Clang, I just get

arch/arm64/kernel/vdso32/../../../arm/vdso/vdsomunge: Not a shared object

Compiling with GCC10 alone is fine.

console-ramoops-0.log

Compile script:= https://github.com/UchihaDev/HyperPlus-Pie/blob/master/build.sh
Source:= https://github.com/UchihaDev/HyperPlus-Pie
Error:= https://del.dog/eralajowop.rb
Device:= Huawei P10 Plus
Compiling with clang-r353983c

Hi the guide is pretty cool. But I met a failure when I make kernel:

make O=out ARCH=x86_64 CC=clang CLANG_TRIPLE=x86_64-linux-gnu x86_64_defconfig

make[1]: Entering directory '/data/kernel-android-emulator/goldfish/out'
  GEN     Makefile
#
# No change to .config
#
make[1]: Leaving directory '/data/kernel-android-emulator/goldfish/out'

make -j64 O=out ARCH=x86_64 CC=clang CLANG_TRIPLE=x86_64-linux-gnu- CROSS_COMPILE=x86_64-linux-android-

root@chrome-server:/data/kernel-android-emulator/goldfish# make -j64 O=out  ARCH=x86_64 CC=clang CLANG_TRIPLE=x86_64-linux-gnu- CROSS_COMPILE=x86_64-linux-android-
make[1]: Entering directory '/data/kernel-android-emulator/goldfish/out'
  GEN     Makefile
scripts/kconfig/conf  --syncconfig Kconfig
scripts/Kconfig.include:39:  gold linker 'x86_64-linux-android-ld' not supported
make[3]: *** [../scripts/kconfig/Makefile:73: syncconfig] Error 1
make[2]: *** [../Makefile:571: syncconfig] Error 2
make[1]: *** [/data/kernel-android-emulator/goldfish/Makefile:691: include/config/auto.conf.cmd] Error 2
make[1]: Leaving directory '/data/kernel-android-emulator/goldfish/out'
make: *** [Makefile:179: sub-make] Error 2
root@chrome-server:/data/kernel-android-emulator/goldfish#

I have not much experience on compiling Android or cross build kernel, so could you please guide me more ? Great thank.

Before the code change, I can cross build kernel 4.19 with gcc, but i have no idea how to do that with CLang.

Thanks
--Yi

i applied the patches from the msm-4.4-pie branch to my kernel https://github.com/Stricted/android_kernel_sony_sdm660/tree/lineage-16.0-clang2

the only conflicts i had were nothing critical and only makefiles related

unfortunately the kernel does not boot (i only get it randomly to boot) with the applied patches regardless if compiled with gcc or clang (without the patches the kernel boots fine when compiled with gcc)
do i miss something?