summaryrefslogtreecommitdiffstats
path: root/conf/nonclangable.conf
Commit message (Collapse)AuthorAgeFilesLines
...
* nvme: Use -Wl,--undefined-version with lldKhem Raj2023-07-271-0/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* nonclangable: Add -Wl,--undefined-version when using lldKhem Raj2023-07-251-0/+100
| | | | | | | | lld does not default to --undefined-version anymore starting with 17.x specifically, this just means we turn on bfd linker compatible link mode for these recipes, which should otherwise be fixed Signed-off-by: Khem Raj <raj.khem@gmail.com>
* babeltrace2: Ignore textrels with lldKhem Raj2023-07-141-0/+3
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* nmap: Use -N option to link when using lld on rv64Khem Raj2023-06-181-1/+4
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* ffmpeg: Enable zbb manip extensions for rv32/rv64Khem Raj2023-05-211-0/+3
| | | | | | | | | | | | | | | | | | This is required with clang after the assembly file is added which uses these instructions. it works with gcc because it uses .option directive to enable zbb extentions in toolchain on the fly clang does not have similar option | <instantiation>:6:21: warning: unknown option, expected 'push', 'pop', 'rvc', 'norvc', 'relax' or 'norelax' | .option arch, +zbb This fixes | src/libavcodec/riscv/bswapdsp_rvb.S:61:9: error: instruction requires the following: 'Zbb' (Basic Bit-Manipulation) or 'Zbkb' (Bitmanip instructions for Cryptography) | rev8 t0, t0 | ^ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* btrfs-tools: Error out on x86 options on non-x86 archesKhem Raj2023-05-111-0/+2
| | | | | | | | e.g. -msha will otherwise be deemed available when using clang which is not correct, therefore treat unused-command-line-argument as error which will be flagged on non-x86 arches Signed-off-by: Khem Raj <raj.khem@gmail.com>
* Revert "webkitgtk: Use gcc for now"Khem Raj2023-03-211-3/+0
| | | | This reverts commit 20a8cff8ba0ce02773946cd7ba398fc08969ce1e.
* frr: Use gcc when compiling for rv32/rv64Khem Raj2023-03-201-0/+3
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* nodejs: Disable enum-constexpr-conversion warning as errorKhem Raj2023-03-201-0/+5
| | | | | | | Clang-16 adds this new warnings which triggers on nodejs, disable it for now Signed-off-by: Khem Raj <raj.khem@gmail.com>
* opengl-es-cts,vulkan-cts,pidgin-sipe: Disable new warnings as errorsKhem Raj2023-03-201-0/+10
| | | | | | | Clang-16 finds more warnings which are treated as errors, lets disable them for now Signed-off-by: Khem Raj <raj.khem@gmail.com>
* nonclangable.conf: Add new exceptions for alternative Linux kernel recipesJon Mason2023-02-221-0/+2
| | | | | | | Other Linux kernel recipes are seeing the same objcopy issue. Add entries for them to work around the issue here as well. Signed-off-by: Jon Mason <jdmason@kudzu.us>
* linux-fslc-imx: Use gnu objcopy with clangKhem Raj2023-02-151-0/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pixman: Use gcc on mipsKhem Raj2023-01-291-0/+2
| | | | | | | libatomic is needed to link after -lomp when -fopenmp is used, it needs clang driver level change Signed-off-by: Khem Raj <raj.khem@gmail.com>
* u-boot-coral: Use gcc toolchainKhem Raj2023-01-091-0/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-fslc-lts: Use binutils objcopyKhem Raj2023-01-091-0/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* mybw: Use gnu objcopy alwaysKhem Raj2023-01-081-6/+4
| | | | | | | Its failing on most of architectures only known working arch seems to be arm Signed-off-by: Khem Raj <raj.khem@gmail.com>
* sysbench: Add -no-integrated-as to cflags with clangKhem Raj2023-01-081-0/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* nonclangable.conf: Use binutils objcopy for BSP kernelsKhem Raj2023-01-041-0/+11
| | | | | | llvm objcopy does not yet work fully for all kernels Signed-off-by: Khem Raj <raj.khem@gmail.com>
* u-boot: Use gcc for variants of u-boot from BSP layersKhem Raj2023-01-041-0/+21
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pixman: Use gcc on aarch64Khem Raj2023-01-041-1/+3
| | | | | | | Some upgrades have regressed pixman with clang on aarch64, until this is sorted, lets use gcc for it as a workaround Signed-off-by: Khem Raj <raj.khem@gmail.com>
* systemd: Add -Wl,--no-warn-rwx-segment with clangKhem Raj2023-01-031-0/+1
| | | | | | Remove the Os workaround, this is no longer needed with systemd 252+ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* ruby,cairo: Add -Wl,--no-warn-rwx-segment with clangKhem Raj2023-01-031-0/+3
| | | | | | | This helps with configure tests which treat this warning as error otherwise Signed-off-by: Khem Raj <raj.khem@gmail.com>
* mybw: Use gnu objcopy on rv32Khem Raj2023-01-031-0/+1
| | | | | | | | Fixes /usr/bin/mybw', 'TOPDIR/build/tmp/work/riscv32-yoe-linux/mybw/0.0+gitAUTOINC+f4bdeee126-r0/package/usr/bin/.debug/mybw']' returned non-zero exit status 1. Subprocess output:riscv32-yoe-linux-llvm-objcopy: error: Link field value 37 in section .rela.dyn is not a symbol table Signed-off-by: Khem Raj <raj.khem@gmail.com>
* nonclangable.conf: Add new exceptionsAleksey Smirnov2022-12-121-1/+10
| | | | | | | | | Add "erlang" for all architectures (found on riscv64 and x86-64) Add "grub" for x86-64 architecture Use proper OBJCOPY for "linux-yocto" for all architectures Signed-off-by: Aleksey Smirnov <aleksey.smirnov@yadro.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
* u-boot: Always use gcc compiler to buildKhem Raj2022-12-051-0/+3
| | | | | | Clang-15 fails to compile u-boot on mips right now. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* linux-yocto: Use gnu objcopy on mipsKhem Raj2022-12-051-0/+3
| | | | | | | Fixes Subprocess output:mips-yoe-linux-llvm-objcopy: error: Link field value 22 in section .rel.dyn is not a symbol table Signed-off-by: Khem Raj <raj.khem@gmail.com>
* rsync: Use gcc for nowKhem Raj2022-11-271-0/+3
| | | | | | | | Needed until [1] is merged into oe-core [1] https://patchwork.yoctoproject.org/project/oe-core/patch/20221123215941.2411460-1-raj.khem@gmail.com/ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* pixman: Do not use clang assembler for nowKhem Raj2022-11-251-0/+1
| | | | | | | | | | | | | Results in assembly file errors e.g. | <instantiation>:1:1: error: unknown directive | .func fname | ^ | <instantiation>:2:1: note: while in macro instantiation | pixman_asm_function fname | ^ Signed-off-by: Khem Raj <raj.khem@gmail.com>
* mybw: USe gnu objcopy on riscv64Khem Raj2022-10-271-0/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* mybw: Use libgcc to link on x86_64Khem Raj2022-10-261-0/+2
| | | | | | | | Fixes x86_64-yoe-linux-ld: /usr/src/debug/glibc/2.36-r0/stdio-common/printf_fphex.c:198: undefined reference to `__letf2' since compiler-rt does not provide the 'tf' functions Signed-off-by: Khem Raj <raj.khem@gmail.com>
* mybw: Use objcopy from binutils on mipsKhem Raj2022-10-221-0/+4
| | | | | | | | | Use libgcc on x86 instead of compiler-rt llvm objcopy errors out so disable it for now Subprocess output:mips-yoe-linux-llvm-objcopy: error: Link field value 42 in section .rel.dyn is not a symbol table Signed-off-by: Khem Raj <raj.khem@gmail.com>
* fmt: Use libgcc on x86_64 as wellKhem Raj2022-10-121-0/+1
| | | | | | | | compiler-rt does not provide the TF functions for x86 or x86_64 since it does not support TF functions on architectures which does not support 128-bit long double. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* fmt: Use libgcc on x86Khem Raj2022-10-031-0/+1
| | | | | | | This is because compiler-rt does not provide int128 builtins which fmt uses Signed-off-by: Khem Raj <raj.khem@gmail.com>
* gnutls,harfbuzz: No need for adding -latomic on rv64Khem Raj2022-09-181-2/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* Revert "concurrencykit: Do not need to use -no-integrated-as anymore on arm"Khem Raj2022-09-181-0/+8
| | | | This reverts commit 320e91209c7000729dfafbc84a72dbd755f18483.
* lttng-ust: Use clang to compile it again on rv64Khem Raj2022-09-181-2/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* mpich: Drop using libgcc unwinder on x86Khem Raj2022-09-181-1/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libbsd: Add more info about the induced errors due to libbsdKhem Raj2022-09-171-0/+2
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* kexec-tools: Do not need -no-integrated-as anymore on x86Khem Raj2022-09-171-8/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* aufs-util,libc-bench: Drop forcing to use libgcc undwinder on armKhem Raj2022-09-171-2/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* concurrencykit: Do not need to use -no-integrated-as anymore on armKhem Raj2022-09-171-8/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libsdl2: Drop using -no-integrated-as on armKhem Raj2022-09-171-6/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libvorbis,mpg123: Drop using -fno-fast-math with clangKhem Raj2022-09-171-4/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* qemu,libffi,openssl: Drop clang kludges for armKhem Raj2022-09-171-17/+0
| | | | | | They are not needed anymore Signed-off-by: Khem Raj <raj.khem@gmail.com>
* openssl: Drop using -no-integrated-asKhem Raj2022-09-171-5/+0
| | | | | | clang-15 is fine without it Signed-off-by: Khem Raj <raj.khem@gmail.com>
* libaio: Drop using -fheinous-gnu-extensionsKhem Raj2022-09-171-4/+0
| | | | | | its not needed anymore Signed-off-by: Khem Raj <raj.khem@gmail.com>
* redis: Re-enable clang on mipsKhem Raj2022-09-171-4/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* mpfr: Use clang again on mips/mips64Khem Raj2022-09-171-4/+0
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* grub: Use clang to compile it on all except aarch64/riscvKhem Raj2022-09-171-2/+9
| | | | | | | | | | | It still fails on aarch64 with many errors like | build-grub-module-verifier: error: sleep: unsupported relocation 0x108. Similar reloc errors seen with grub-efi on rv32 as well on rv64 clang crashes :( Signed-off-by: Khem Raj <raj.khem@gmail.com>
* kexec-tools-klibc: Unbolt workaround for 53998Khem Raj2022-09-171-3/+0
| | | | | | This is fixed upstream Signed-off-by: Khem Raj <raj.khem@gmail.com>