| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
using LTO.
Referring to lto.inc in openembedded-core, when using lto, the LTO variable is added to SELECTED_OPTIMIZATION.
In this case, with the clang toolchain, -fuse-ld=lld is added when using -flto,
but the -fuse-ld=lld option is sufficient as a linker flag.
If -fuse-ld=lld is present in CFLAGS, an unused-command-line-argument warning occurs.
In recipes that treat this warning as an error, the build fails.
aarch64-yoe-linux-clang: error: argument unused during compilation: '-fuse-ld=lld' [-Werror,-Wunused-command-line-argument]
See more details https://errors.yoctoproject.org/Errors/Details/886599
Signed-off-by: mark.yang <mark.yang@lge.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When enabling LTO in the clang toolchain, .o files are generated in LLVM IR bitcode format instead of ELF format.
In this case, dwarfsrcfiles fails in do_package.
See more details at: https://errors.yoctoproject.org/Errors/Details/886597
```
dwarfsrcfiles: TOPDIR/build/tmp/work/cortexa72-yoe-linux/libcxx/21.1.4/package/usr/lib/libc++experimental.a: not a valid ELF file
```
As already discussed on the mailing list https://www.mail-archive.com/yocto@lists.yoctoproject.org/msg15501.html,
setting `INHIBIT_PACKAGE_DEBUG_SPLIT = "1"` disables debug splitting.
It is not desirable to disable debug splitting just to avoid the dwarfsrcfiles error.
A simple solution, as Khem Raj suggested in the lto.inc file of openembedded-core,
is to add the `-ffat-lto-objects` flag to the LTO settings.
This keeps both IR bitcode and ELF format, preventing the error.
Signed-off-by: mark.yang <mark.yang@lge.com>
|
| |
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
| |
clang runtime recipe set them rightly in core
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
| |
This is better fixed in recipes if needed now that
clang is a core recipe.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
| |
This is gone from OE-core so good riddance
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
| |
These are not supported by clang, but now they are handled in core
tune files.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
| |
This should be part of default tune infra in core
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
| |
Its moved into klibc.bbclass in meta-initramfs
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
|
| |
Some of these settings are moved to OE-core and some are deferred to
distros where it belongs. This makes meta-clang compatible with YP
again.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
|
| |
options should be in sync or else clang will not link the binaries
| x86_64-yoesdk-linux-clang: error: --rtlib=libgcc requires --unwindlib=libgcc
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
| |
It will add these options to gcc as well when building native recipes
as it is implemented in oe-core, this logic is different so adjust
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
| |
TOOLCHAIN is possible to set for target/native/nativesdk separately
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
| |
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
| |
|
|
|
|
|
|
| |
clang.bbclass in oe-core will define toolchain-gcc for nativesdk
and thats perhaps better, ideally we should depend on llvm runtime
unconditionally, so a package can use either llvm or gcc runtimes
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|
|
|
A similar bbclass is added to oe-core, so rename it as legacy class
Signed-off-by: Khem Raj <raj.khem@gmail.com>
|