<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-clang.git, branch styhead</title>
<subtitle>Mirror of github.com/kraj/meta-clang.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-clang.git/atom?h=styhead</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-clang.git/atom?h=styhead'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/'/>
<updated>2024-10-25T16:09:04+00:00</updated>
<entry>
<title>clang_git.bb: assign PYTHON_PN to LLDB_PYTHON_EXE_RELATIVE_PATH</title>
<updated>2024-10-25T16:09:04+00:00</updated>
<author>
<name>Jan Kircher</name>
<email>jan.kircher@leica-microsystems.com</email>
</author>
<published>2024-10-23T14:52:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=c709a5196f1e8654425b43b478064395386c36d4'/>
<id>urn:sha1:c709a5196f1e8654425b43b478064395386c36d4</id>
<content type='text'>
Signed-off-by: Jan Kircher &lt;jan.kircher@leica-microsystems.com&gt;
</content>
</entry>
<entry>
<title>u-boot: u-boot is clangable</title>
<updated>2024-10-08T06:38:20+00:00</updated>
<author>
<name>Jon Mason</name>
<email>jdmason@kudzu.us</email>
</author>
<published>2024-09-30T18:11:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=e875cdfc91a8ddb363fb8fbf297a6af867dfeea8'/>
<id>urn:sha1:e875cdfc91a8ddb363fb8fbf297a6af867dfeea8</id>
<content type='text'>
Since clang is at version 19 now, remove the blocking of building
u-boot.  I'm not seeing any issues with building u-boot and running
testimage for qemuarm, qemuarm64, and qemumips.
Based on the original comment, this limitation probably should've been
only applied to mips.

Leaving the BSP versions of u-boot in nonclangable, as I don't know if
those have issues or not, and thought it better to err on the side of
caution.

Signed-off-by: Jon Mason &lt;jdmason@kudzu.us&gt;
</content>
</entry>
<entry>
<title>Revert "vte: Use libstdc++ when using clang"</title>
<updated>2024-09-30T19:18:39+00:00</updated>
<author>
<name>Ross Burton</name>
<email>ross.burton@arm.com</email>
</author>
<published>2024-09-30T14:09:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=036ca8256d2e62ce153b6cba40ee03efd1d02633'/>
<id>urn:sha1:036ca8256d2e62ce153b6cba40ee03efd1d02633</id>
<content type='text'>
This issue has been resolved upstream:

https://gitlab.gnome.org/GNOME/vte/-/commit/c8838779d5f8c0e03411cef9775cd8f5a10a6204

This reverts commit 70295d739f830a8d2abb2ad961e1c544f01be197.

Signed-off-by: Ross Burton &lt;ross.burton@arm.com&gt;
</content>
</entry>
<entry>
<title>clang: Do not package clang-pseudo clang-pseudo-gen and clang-rename</title>
<updated>2024-09-26T22:39:25+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2024-09-26T04:25:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=32c4e622bd723abf08753a0f7720a4b4064d8f95'/>
<id>urn:sha1:32c4e622bd723abf08753a0f7720a4b4064d8f95</id>
<content type='text'>
These tools are unmaintained and clang-20+ has removed them [1] [2]

[1] https://github.com/llvm/llvm-project/commit/ed8f78827895050442f544edef2933a60d4a7935
[2] https://github.com/llvm/llvm-project/commit/40c45b6b43180221acb49f387e7d3158adf49e3e

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>vte: Disable gi data generation when using clang</title>
<updated>2024-09-25T06:49:10+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2024-09-24T13:20:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=1628f0f7c05439001a8425bd37f5899b49a61e21'/>
<id>urn:sha1:1628f0f7c05439001a8425bd37f5899b49a61e21</id>
<content type='text'>
Somehow clang built binaries used in intermediate step crashes the qemu
user mode.

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>vte: Use libstdc++ when using clang</title>
<updated>2024-09-25T06:49:10+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2024-09-23T23:44:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=70295d739f830a8d2abb2ad961e1c544f01be197'/>
<id>urn:sha1:70295d739f830a8d2abb2ad961e1c544f01be197</id>
<content type='text'>
It does not build with libc++ anymore.

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>qtwebengine: Use clang for native toolchain as well</title>
<updated>2024-09-19T20:42:20+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2024-09-19T20:39:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=f3cf775413863c61121911ca83e72bee9e27ec29'/>
<id>urn:sha1:f3cf775413863c61121911ca83e72bee9e27ec29</id>
<content type='text'>
This makes the chromium build less confused when mixing
native compiler for gcc and target compiler for clang
this does not sit well with gn build system and it starts
to pass clang options to gcc, which does not always work

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>python3-cffi: Ad clang to rdeps for ptests to pass</title>
<updated>2024-09-18T14:32:26+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2024-09-18T05:05:21+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=c6a3ab111cee74509f4c3200c4340ba795ea6242'/>
<id>urn:sha1:c6a3ab111cee74509f4c3200c4340ba795ea6242</id>
<content type='text'>
ptest tries to compile some portions on the target
and demands the compiler that was used to cross-compile it

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>python3-drgn: Use gcc when compiling for riscv32</title>
<updated>2024-09-18T14:32:26+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2024-09-17T06:46:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=b59d0cf608f6fdbb86069ca0fb79c49d1b9377bc'/>
<id>urn:sha1:b59d0cf608f6fdbb86069ca0fb79c49d1b9377bc</id>
<content type='text'>
openmp port for riscv32 is not yet available so we
can not use clang for it for now.

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
<entry>
<title>nmap: Remove LLD build workaround for RISCV-64</title>
<updated>2024-09-18T14:32:26+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2024-09-16T02:22:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-clang.git/commit/?id=04c93873f4c98d7a62dcb1c26a0c2ecc3117292b'/>
<id>urn:sha1:04c93873f4c98d7a62dcb1c26a0c2ecc3117292b</id>
<content type='text'>
This is no longer needed with clang-19

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
</content>
</entry>
</feed>
