<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-clang.git/conf, branch master</title>
<subtitle>Mirror of github.com/kraj/meta-clang.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-clang.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-clang.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/'/>
<updated>2026-10-28T02:56:45+00:00</updated>
<entry>
<title>lrzsz: Disable unused-but-set-global warning</title>
<updated>2026-10-28T02:56:45+00:00</updated>
<author>
<name>Khem Raj</name>
<email>khem.raj@oss.qualcomm.com</email>
</author>
<published>2026-10-27T20:45:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=555882484074bbc97f3bd2e6ced7c34f1ad548f8'/>
<id>urn:sha1:555882484074bbc97f3bd2e6ced7c34f1ad548f8</id>
<content type='text'>
Signed-off-by: Khem Raj &lt;khem.raj@oss.qualcomm.com&gt;
</content>
</entry>
<entry>
<title>nonclangable.conf: Drop obsolete riscv workarounds</title>
<updated>2026-10-28T02:56:45+00:00</updated>
<author>
<name>Khem Raj</name>
<email>khem.raj@oss.qualcomm.com</email>
</author>
<published>2026-10-25T08:35:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=5f15046f34fd1bd6d892df11c5ac8e7b8f6f2fe0'/>
<id>urn:sha1:5f15046f34fd1bd6d892df11c5ac8e7b8f6f2fe0</id>
<content type='text'>
Remove the riscv toolchain workarounds that are no longer needed with
current clang:

- mesa: stop pinning gcc on riscv64
- frr: stop pinning gcc on riscv64 and riscv32 (llvm-project#61412)
- ffmpeg: stop appending -march=rv64gczbb/rv32gczbb, which also made
  the binaries require Zbb on plain rv64gc/rv32gc tunes
- dav1d: stop building with -no-integrated-as on riscv64

AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj &lt;khem.raj@oss.qualcomm.com&gt;
</content>
</entry>
<entry>
<title>nonclangable.conf: Build grub and grub-efi with clang on riscv64</title>
<updated>2026-10-28T02:56:45+00:00</updated>
<author>
<name>Khem Raj</name>
<email>khem.raj@oss.qualcomm.com</email>
</author>
<published>2026-10-25T08:00:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=e0e180f018bbee9d654ecf2b627d04577c8fa674'/>
<id>urn:sha1:e0e180f018bbee9d654ecf2b627d04577c8fa674</id>
<content type='text'>
The gcc pins were added for a clang-15 crash; drop them so grub and
grub-efi use the default toolchain on riscv64 again.

AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj &lt;khem.raj@oss.qualcomm.com&gt;
</content>
</entry>
<entry>
<title>nonclangable.conf: Stop forcing RVV for python3-numpy on riscv</title>
<updated>2026-10-28T02:56:45+00:00</updated>
<author>
<name>Khem Raj</name>
<email>khem.raj@oss.qualcomm.com</email>
</author>
<published>2026-10-25T06:18:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=c69e53d4adf827821fbcddd4ae07c629327723ee'/>
<id>urn:sha1:c69e53d4adf827821fbcddd4ae07c629327723ee</id>
<content type='text'>
Appending -march=rv64gcv (rv32gcv) to TOOLCHAIN_OPTIONS made every object
in numpy require the vector extension, not just its RVV dispatch targets.
On rv64gc tunes the result crashes with SIGILL as soon as
_multiarray_umath is loaded on a CPU or kernel without V, e.g. a
std::unordered_map constructor in a static initializer is vectorised:

  vsetivli zero,2,e64,m1,ta,ma

This breaks the python3-fsspec ptest (via pandas -&gt; numpy) on
qemuriscv64, whose linux-yocto kernel has CONFIG_RISCV_ISA_V unset.

numpy's meson build already compiles the RVV dispatch sources with
-march=rv64gcv on its own (baseline: none, dispatch: RVV), and the
highway __riscv_vsetvl_e8mf8 error this worked around for numpy 2.2.3
no longer happens with numpy 2.5.4 and clang 23.

AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj &lt;khem.raj@oss.qualcomm.com&gt;
</content>
</entry>
<entry>
<title>nonclangable.conf: re-enable g-i for libmodulemd/webkitgtk on clang x86-64</title>
<updated>2026-09-26T20:22:31+00:00</updated>
<author>
<name>Khem Raj</name>
<email>khem.raj@oss.qualcomm.com</email>
</author>
<published>2026-09-26T00:34:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=a2c51ce7e4b582a358b707e5c144c05690d2cf71'/>
<id>urn:sha1:a2c51ce7e4b582a358b707e5c144c05690d2cf71</id>
<content type='text'>
GI_DATA_ENABLED was forced False for these two on toolchain-clang:x86-64
to work around g-ir-scanner crashing while parsing glibc 2.41 headers
under clang. Verified with clean from-scratch rebuilds of both (clang
23.1.1, glibc 2.44+git, forcing GI_DATA_ENABLED back to True) that
g-ir-scanner/g-ir-compiler now complete cleanly and produce their
.gir/.typelib files with no errors, so the workaround is stale here.

This unblocks sushi, whose html.blp requires the WebKit-6.0 typelib
that webkitgtk only produces when introspection is enabled.

libblockdev, webkitgtk3, and the 32-bit x86 entries are left as-is
since they were not re-verified.

AI-Generated: Uses Claude Code
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>conf/layer.conf: Support Blacksail</title>
<updated>2026-09-24T14:05:05+00:00</updated>
<author>
<name>Leon Anavi</name>
<email>leon.anavi@konsulko.com</email>
</author>
<published>2026-09-24T13:03:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=8eba865e80f53426778df49f6255945c282a7738'/>
<id>urn:sha1:8eba865e80f53426778df49f6255945c282a7738</id>
<content type='text'>
Set the layer compatibility to the Yocto Project release Blacksail
following the recent change in openembedded-core:
https://git.openembedded.org/openembedded-core/commit/?id=37623ffbdd34a5c6b3e12ee33195f8e82343f198

Fixes:

ERROR: Layer clang-layer is not compatible with the core layer
which only supports these series: blacksail (layer is compatible
with wrynose)

This work was sponsored by GOVCERT.LU.

Signed-off-by: Leon Anavi &lt;leon.anavi@konsulko.com&gt;
</content>
</entry>
<entry>
<title>nonclangable.conf: Pin perf via KERNEL_TOOLCHAIN instead of TOOLCHAIN</title>
<updated>2026-07-27T23:29:54+00:00</updated>
<author>
<name>Khem Raj</name>
<email>khem.raj@oss.qualcomm.com</email>
</author>
<published>2026-07-27T17:19:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=e7ff013afaa78f639a3edf1627ce5c186ad87c0a'/>
<id>urn:sha1:e7ff013afaa78f639a3edf1627ce5c186ad87c0a</id>
<content type='text'>
perf inherits kernel-arch, which since oe-core 0e3756efe0 ("kernel-arch:
add KERNEL_TOOLCHAIN to switch the whole kernel toolchain") sets

  KERNEL_TOOLCHAIN ?= "gcc"
  TOOLCHAIN = "${KERNEL_TOOLCHAIN}"

bitbake's basehash records the unexpanded value of a variable along with
its dependency set, not just the final expansion. Overriding TOOLCHAIN
here replaced '${KERNEL_TOOLCHAIN}' with the literal 'gcc' and dropped
the recorded dependency on KERNEL_TOOLCHAIN, so merely adding this layer
changed perf's basehash even though the resulting toolchain is identical.

yocto-check-layer flags that as the layer altering OE-Core signatures:

  AssertionError: Adding layer meta-clang changed signatures.
  9 signatures changed [...]
    List of dependencies for variable TOOLCHAIN changed from
      'frozenset({'KERNEL_TOOLCHAIN'})' to 'frozenset()'
    Dependency on Variable KERNEL_TOOLCHAIN was removed
    Variable TOOLCHAIN value changed from '${KERNEL_TOOLCHAIN}' to 'gcc'

Pin KERNEL_TOOLCHAIN instead. TOOLCHAIN then stays byte-identical to the
OE-Core baseline, so the signatures match, while perf is still forced to
gcc for anyone setting KERNEL_TOOLCHAIN = "clang".

Signed-off-by: Khem Raj &lt;khem.raj@oss.qualcomm.com&gt;
</content>
</entry>
<entry>
<title>conf/layer.conf: remove unused BBFILES_DYNAMIC entries</title>
<updated>2026-06-16T05:16:55+00:00</updated>
<author>
<name>Deepesh Varatharajan</name>
<email>Deepesh.Varatharajan@windriver.com</email>
</author>
<published>2026-06-03T08:22:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=0baedd06e78d26d3b927471cfd91960b7229a178'/>
<id>urn:sha1:0baedd06e78d26d3b927471cfd91960b7229a178</id>
<content type='text'>
Remove stale dynamic layer references (browser-layer, networking-layer,
meta-python, qt5-layer) from BBFILES_DYNAMIC in layer.conf.

These directories no longer exist under dynamic-layers/, so the
patterns are dead code and have no effect.

Signed-off-by: Deepesh Varatharajan &lt;Deepesh.Varatharajan@windriver.com&gt;
</content>
</entry>
<entry>
<title>swupdate: Pin to use gcc</title>
<updated>2026-06-03T08:44:17+00:00</updated>
<author>
<name>Khem Raj</name>
<email>khem.raj@oss.qualcomm.com</email>
</author>
<published>2026-05-23T15:45:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=4b18f531a8d1047f49dd3097ddd00be870c0ed1e'/>
<id>urn:sha1:4b18f531a8d1047f49dd3097ddd00be870c0ed1e</id>
<content type='text'>
2025.12 does not compile with clang sadly

Signed-off-by: Khem Raj &lt;khem.raj@oss.qualcomm.com&gt;
</content>
</entry>
<entry>
<title>layer.conf: Add wrynose (yocto 6.0) to compatible layers</title>
<updated>2026-03-18T21:50:12+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2026-03-18T05:52:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=b044647662a6916299238e7f2d9476d54f528263'/>
<id>urn:sha1:b044647662a6916299238e7f2d9476d54f528263</id>
<content type='text'>
Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
</feed>
