Go to file
Khem Raj ea8387ba41
nss: Fix build when using clang toolchain
When using clang cross compiler, nss make system adds
some clang specific options e.g. Qunused-options to CFLAGS
which is fine for cross/target compile but some portions e.g.
nsinstall is build natively so it uses NATIVE_CC to compile this
utility, its is set to BUILD_CC rightly but when using clang for CC
and gcc for BUILD_CC, nss build system is confused because its
trying to use the computed set of warnings for both native and cross
compile and they may not match between clang and gcc. So here we
explicitly use clang for NATIVE_CC when TOOLCHAIN is clang

Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-07-17 19:14:31 -07:00
contrib contrib: oe-stylize: Use Python3 explicitly 2023-06-04 22:29:46 -07:00
meta-filesystems ufs-utils: upgrade 7.14.11 -> 7.14.12 2025-07-17 09:24:54 -07:00
meta-gnome libdex: upgrade 0.10.0 -> 0.10.1 2025-07-08 23:40:28 -07:00
meta-initramfs dracut: add 'git' recipe with DEFAULT_PREFERENCE = -1 2025-07-04 09:42:10 -07:00
meta-multimedia libmusicbrainz: Upgrade to tip of trunk 2025-07-15 23:54:14 -07:00
meta-networking mbedtls: upgrade 3.6.3.1 -> 3.6.4 2025-07-16 08:52:06 -07:00
meta-oe nss: Fix build when using clang toolchain 2025-07-17 19:14:31 -07:00
meta-perl libhtml-parser-perl: upgrade 3.72 -> 3.73 2025-07-12 13:50:00 -07:00
meta-python python3-charset-normalizer: Update mypy 2025-07-17 08:53:08 -07:00
meta-webserver apache2: upgrade 2.4.63 -> 2.4.64 2025-07-15 23:54:14 -07:00
meta-xfce xfce4-screenshooter: Upgrade to 1.11.2 2025-07-16 08:52:06 -07:00
.b4-config Add toplevel b4 config file 2025-04-10 08:31:06 -07:00
.gitignore .gitignore: add *.pyc and *.pyo 2019-06-15 16:45:33 -07:00
COPYING.MIT add README and license for this layer 2011-02-13 16:47:32 +01:00
README.md layers: Move READMEs to markdown format 2023-06-17 08:30:01 -07:00

Collection of layers for the OE-core universe

Main layer maintainer: Khem Raj raj.khem@gmail.com

This repository is a collection of layers to suppliment OE-Core with additional packages, Each layer have designated maintainer Please see the respective READMEs in the layer subdirectories